Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 025fa8d4d182ddf3c62264ddf5d9b2a03cf3aa19f077117ec46dccf45a0b8884

Tx prefix hash: 57188432c2f725f054ebba3fdfbd6b297dc358c5b02d7670d6a16e4e4da7ac8e
Tx public key: e3930411b36675a9e53300f1fb2118723c649d90dadd0b8f6052eb077cbe1eb5
Timestamp: 1730658172 Timestamp [UCT]: 2024-11-03 18:22:52 Age [y:d:h:m:s]: 00:061:19:28:48
Block: 1145834 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 44235 RingCT/type: yes/0
Extra: 01e3930411b36675a9e53300f1fb2118723c649d90dadd0b8f6052eb077cbe1eb50211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ef980e88e04564fcce1ee0d72621812e75e8486ed85e3c88a39dc6fbda19a47b 0.600000000000 1630359 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": 1145844, "vin": [ { "gen": { "height": 1145834 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ef980e88e04564fcce1ee0d72621812e75e8486ed85e3c88a39dc6fbda19a47b" } } ], "extra": [ 1, 227, 147, 4, 17, 179, 102, 117, 169, 229, 51, 0, 241, 251, 33, 24, 114, 60, 100, 157, 144, 218, 221, 11, 143, 96, 82, 235, 7, 124, 190, 30, 181, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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