Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a9a6682655b788e482ddc3f7b1ea862ffb95aebc8523fb46e1a2ef8c3b509fa7

Tx prefix hash: cd8fc181b517ac8dec5c2baa0be79659bf27bc60d5c86de9ab528afca9796e29
Tx public key: 083d82826b8fc63d3e268b203938c3f6108d6304997f2d40870b21b1785109cf
Timestamp: 1721026881 Timestamp [UCT]: 2024-07-15 07:01:21 Age [y:d:h:m:s]: 00:266:04:51:39
Block: 1066080 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190164 RingCT/type: yes/0
Extra: 01083d82826b8fc63d3e268b203938c3f6108d6304997f2d40870b21b1785109cf021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b3bd52f5440649d3d6e3d857fdda090a81883a4758c1f1aaa73858e4fd967c44 0.600000000000 1536651 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": 1066090, "vin": [ { "gen": { "height": 1066080 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b3bd52f5440649d3d6e3d857fdda090a81883a4758c1f1aaa73858e4fd967c44" } } ], "extra": [ 1, 8, 61, 130, 130, 107, 143, 198, 61, 62, 38, 139, 32, 57, 56, 195, 246, 16, 141, 99, 4, 153, 127, 45, 64, 135, 11, 33, 177, 120, 81, 9, 207, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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