Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6212af47ffd5b735e8df07cf6d31f7e002b3d18bf4bd2b5570e2dab8f621543a

Tx prefix hash: 760b7b6db4d4d74feafcd4a979b950920e88a250c8053186069b41d551f09309
Tx public key: 237c67662c5236b97a936585124c30f971a2de0f239f3da448ba9688f07ea748
Timestamp: 1750969391 Timestamp [UCT]: 2025-06-26 20:23:11 Age [y:d:h:m:s]: 00:136:21:31:19
Block: 1313396 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95843 RingCT/type: yes/0
Extra: 01237c67662c5236b97a936585124c30f971a2de0f239f3da448ba9688f07ea74802110000000201491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9c80e4078c3b80a7f26117aac2c396b955da60c7a2aeb2d0ed9ceee430a71b04 0.600000000000 1801035 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": 1313406, "vin": [ { "gen": { "height": 1313396 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9c80e4078c3b80a7f26117aac2c396b955da60c7a2aeb2d0ed9ceee430a71b04" } } ], "extra": [ 1, 35, 124, 103, 102, 44, 82, 54, 185, 122, 147, 101, 133, 18, 76, 48, 249, 113, 162, 222, 15, 35, 159, 61, 164, 72, 186, 150, 136, 240, 126, 167, 72, 2, 17, 0, 0, 0, 2, 1, 73, 31, 136, 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