Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 01cfca1c29584dd32b7ad1bb1ec10152afc3dcfd478b2ff3a85f81ca16b0afc9

Tx prefix hash: bff9bbb2eeaab867ba1a780736900775e098eaf5cc796638379502374b31486e
Tx public key: 4d9e69a204c1e53d798d7c044c07aaed3dff7f5a5a5403754bb0bcf3ad7041c4
Timestamp: 1732032134 Timestamp [UCT]: 2024-11-19 16:02:14 Age [y:d:h:m:s]: 00:138:02:10:10
Block: 1157218 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98495 RingCT/type: yes/0
Extra: 014d9e69a204c1e53d798d7c044c07aaed3dff7f5a5a5403754bb0bcf3ad7041c4021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eb0989d7da0b69b19515f7dc305edd7d454b466e78718d5b499d3b40d95b5d8d 0.600000000000 1642841 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": 1157228, "vin": [ { "gen": { "height": 1157218 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb0989d7da0b69b19515f7dc305edd7d454b466e78718d5b499d3b40d95b5d8d" } } ], "extra": [ 1, 77, 158, 105, 162, 4, 193, 229, 61, 121, 141, 124, 4, 76, 7, 170, 237, 61, 255, 127, 90, 90, 84, 3, 117, 75, 176, 188, 243, 173, 112, 65, 196, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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