Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 606605a42979c07559d242b0f8378f5a2378b8c645b66141ed7f4463cc2ac8f3

Tx prefix hash: 3aaa43024ece72ee9eba8a97eefb5b7d75c193f88936611a5601465b493ba435
Tx public key: b57cb422f1529b647b26b9b067d4ea950193f9a70d0a34fda028db7b45ccee70
Timestamp: 1765328813 Timestamp [UCT]: 2025-12-10 01:06:53 Age [y:d:h:m:s]: 00:028:03:39:15
Block: 1430215 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 20160 RingCT/type: yes/0
Extra: 01b57cb422f1529b647b26b9b067d4ea950193f9a70d0a34fda028db7b45ccee7002110000000470609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 888ded1d2af6b248dc4597cc5c393365ea904f632e878d535f68a396d4839641 0.600000000000 1918962 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": 1430225, "vin": [ { "gen": { "height": 1430215 } } ], "vout": [ { "amount": 600000000, "target": { "key": "888ded1d2af6b248dc4597cc5c393365ea904f632e878d535f68a396d4839641" } } ], "extra": [ 1, 181, 124, 180, 34, 241, 82, 155, 100, 123, 38, 185, 176, 103, 212, 234, 149, 1, 147, 249, 167, 13, 10, 52, 253, 160, 40, 219, 123, 69, 204, 238, 112, 2, 17, 0, 0, 0, 4, 112, 96, 157, 3, 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