Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 43123cba5f1a27008dee8cf379e8117eaecefab247473e26efb0cc3a3f0ef375

Tx prefix hash: 1afc47d38b8ab0eef9a3e94d99220b764e06b76dc495f236677a0897b3099a49
Tx public key: bb74708804b9f9e3eabdea16d858db6464f05bbd4c2728917b5670398b549729
Timestamp: 1708785352 Timestamp [UCT]: 2024-02-24 14:35:52 Age [y:d:h:m:s]: 01:037:18:27:53
Block: 964584 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287998 RingCT/type: yes/0
Extra: 01bb74708804b9f9e3eabdea16d858db6464f05bbd4c2728917b5670398b5497290211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a5a387ffd907abbd0e4b1f8b4517aa08eaac6d7fd35edf524b64fd1cb04688eb 0.600000000000 1424325 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": 964594, "vin": [ { "gen": { "height": 964584 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a5a387ffd907abbd0e4b1f8b4517aa08eaac6d7fd35edf524b64fd1cb04688eb" } } ], "extra": [ 1, 187, 116, 112, 136, 4, 185, 249, 227, 234, 189, 234, 22, 216, 88, 219, 100, 100, 240, 91, 189, 76, 39, 40, 145, 123, 86, 112, 57, 139, 84, 151, 41, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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