Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c5d7a0209665a549b533dc91122d14d517fc2fccdd593485cc07d63de3ada489

Tx prefix hash: 5e21f539bf53cc4614e08f6c7f5191537917017725c1e47b4ed080a3f4b6e66c
Tx public key: aa1bb5da1dc5480b1b28c00474c5dd14672f52a694ad734a816c2ec599fd63d1
Timestamp: 1730013167 Timestamp [UCT]: 2024-10-27 07:12:47 Age [y:d:h:m:s]: 00:027:20:12:47
Block: 1140536 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 19882 RingCT/type: yes/0
Extra: 01aa1bb5da1dc5480b1b28c00474c5dd14672f52a694ad734a816c2ec599fd63d102110000000e007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 67c6566804d9e71c9a56594b9243738b27706c9dae60d7ee6d48105b8cf91514 0.600000000000 1624337 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": 1140546, "vin": [ { "gen": { "height": 1140536 } } ], "vout": [ { "amount": 600000000, "target": { "key": "67c6566804d9e71c9a56594b9243738b27706c9dae60d7ee6d48105b8cf91514" } } ], "extra": [ 1, 170, 27, 181, 218, 29, 197, 72, 11, 27, 40, 192, 4, 116, 197, 221, 20, 103, 47, 82, 166, 148, 173, 115, 74, 129, 108, 46, 197, 153, 253, 99, 209, 2, 17, 0, 0, 0, 14, 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