Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9981990e51379f3948f113312dc1d04750f99f919d1f11d7cb86f350e2980d1a

Tx prefix hash: 73f93fb2aed8ba01960cc38748c361f7f940ddff07c80717ea5c6b84169037f3
Tx public key: e7aae7736dfd5a07e0c4ec34b47fb7bc4a840ea23b6bfd7f80cc6352e1c80076
Timestamp: 1713544284 Timestamp [UCT]: 2024-04-19 16:31:24 Age [y:d:h:m:s]: 01:024:21:50:56
Block: 1004027 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 278777 RingCT/type: yes/0
Extra: 01e7aae7736dfd5a07e0c4ec34b47fb7bc4a840ea23b6bfd7f80cc6352e1c8007602110000000e0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d96797988b8fabbb929fef6cdb42770335ebaf39bad4f9d4960378c6b570fa07 0.600000000000 1464589 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": 1004037, "vin": [ { "gen": { "height": 1004027 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d96797988b8fabbb929fef6cdb42770335ebaf39bad4f9d4960378c6b570fa07" } } ], "extra": [ 1, 231, 170, 231, 115, 109, 253, 90, 7, 224, 196, 236, 52, 180, 127, 183, 188, 74, 132, 14, 162, 59, 107, 253, 127, 128, 204, 99, 82, 225, 200, 0, 118, 2, 17, 0, 0, 0, 14, 0, 17, 5, 91, 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