Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 72d53e2f45c8560df359790f0495baee43201dce649b3d29d649a1545781ee59

Tx prefix hash: eed6609461c870d856cc58e1aae4d9f2528f2cf3a264a2340512bb7d8b3493b8
Tx public key: bf7c49e95e013499a6baa715b55f89ee1cf24a252f6fbbb5fa7dda16509d39f8
Timestamp: 1749891138 Timestamp [UCT]: 2025-06-14 08:52:18 Age [y:d:h:m:s]: 00:156:14:12:00
Block: 1304732 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109672 RingCT/type: yes/0
Extra: 01bf7c49e95e013499a6baa715b55f89ee1cf24a252f6fbbb5fa7dda16509d39f802110000000443846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 77cba2f788824f147f39f216f0df3a8f9fbda2849049516b9960486dc84231c6 0.600000000000 1792323 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": 1304742, "vin": [ { "gen": { "height": 1304732 } } ], "vout": [ { "amount": 600000000, "target": { "key": "77cba2f788824f147f39f216f0df3a8f9fbda2849049516b9960486dc84231c6" } } ], "extra": [ 1, 191, 124, 73, 233, 94, 1, 52, 153, 166, 186, 167, 21, 181, 95, 137, 238, 28, 242, 74, 37, 47, 111, 187, 181, 250, 125, 218, 22, 80, 157, 57, 248, 2, 17, 0, 0, 0, 4, 67, 132, 109, 102, 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