Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c166ec5838efbfc0cc0e5168b8d57c676e3e843bef8674baf17f975fcb831659

Tx prefix hash: c197b0253f1d84e08ad13946770365c5922fcd097d02324fa5488098936a85c6
Tx public key: 5d4449568d8232df12c812a4eda2c2e8a9d41acf4a16024ae6c379a23264ef6c
Timestamp: 1705281896 Timestamp [UCT]: 2024-01-15 01:24:56 Age [y:d:h:m:s]: 01:304:06:20:09
Block: 935504 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 476305 RingCT/type: yes/0
Extra: 015d4449568d8232df12c812a4eda2c2e8a9d41acf4a16024ae6c379a23264ef6c02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2da8ca5c5942a70b86b33433976a223b40744d062f21ca0c7a4235b26c1a77e7 0.600000000000 1393520 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": 935514, "vin": [ { "gen": { "height": 935504 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2da8ca5c5942a70b86b33433976a223b40744d062f21ca0c7a4235b26c1a77e7" } } ], "extra": [ 1, 93, 68, 73, 86, 141, 130, 50, 223, 18, 200, 18, 164, 237, 162, 194, 232, 169, 212, 26, 207, 74, 22, 2, 74, 230, 195, 121, 162, 50, 100, 239, 108, 2, 17, 0, 0, 0, 1, 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