Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 8af07137568550d6c80fbe4ca9149fd66c0fb76ee4dac8e0bfb021063f25da36

Tx prefix hash: 499e1e2069a4122623eb22dc656df7356c274568a1656cb6c98a1513fdc14c72
Tx public key: 317a30a3c64a667576d1ccaef1fbb8d170f312a6caba2ed587168844b194193d
Timestamp: 1754910176 Timestamp [UCT]: 2025-08-11 11:02:56 Age [y:d:h:m:s]: 00:108:19:23:26
Block: 1344755 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77032 RingCT/type: yes/0
Extra: 01317a30a3c64a667576d1ccaef1fbb8d170f312a6caba2ed587168844b194193d02110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f79e801e3ff28d3bf5cb4fa0d660a46cdf4f0dc0dc21ac71a30245d25b6f4e02 0.600000000000 1832640 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1344765, "vin": [ { "gen": { "height": 1344755 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f79e801e3ff28d3bf5cb4fa0d660a46cdf4f0dc0dc21ac71a30245d25b6f4e02" } } ], "extra": [ 1, 49, 122, 48, 163, 198, 74, 102, 117, 118, 209, 204, 174, 241, 251, 184, 209, 112, 243, 18, 166, 202, 186, 46, 213, 135, 22, 136, 68, 177, 148, 25, 61, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8