Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1959feb10b0bbb7f02960c920cab6620719d97fd7540251981771a32c20b823b

Tx prefix hash: 60fd9162c91e2ab21551f0c878ce651bca4690f91521f66c1434a06f1aec12a3
Tx public key: aa49907b0c7bac1ec7459b80c2eebf3f1d6a68e27ff5dc208308d8460bf9ca98
Timestamp: 1712598707 Timestamp [UCT]: 2024-04-08 17:51:47 Age [y:d:h:m:s]: 01:053:15:50:24
Block: 996161 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 299383 RingCT/type: yes/0
Extra: 01aa49907b0c7bac1ec7459b80c2eebf3f1d6a68e27ff5dc208308d8460bf9ca9802110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b483b624f5eafb7dae3908a873e339274d16f67e6bbe12345bc6ef747dabdf5a 0.600000000000 1456577 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": 996171, "vin": [ { "gen": { "height": 996161 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b483b624f5eafb7dae3908a873e339274d16f67e6bbe12345bc6ef747dabdf5a" } } ], "extra": [ 1, 170, 73, 144, 123, 12, 123, 172, 30, 199, 69, 155, 128, 194, 238, 191, 63, 29, 106, 104, 226, 127, 245, 220, 32, 131, 8, 216, 70, 11, 249, 202, 152, 2, 17, 0, 0, 0, 7, 82, 212, 126, 148, 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