Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2bc008fa25a83c1a16cf0688a8b57d35fcb119a36806aadc7c903dca9b1fe83

Tx prefix hash: 76b3d13e4327ceb176a1ee34b68787dac2da1996da6fef395e8ab96bc328f64d
Tx public key: 79d5207a0408ae4d5480aaee961fd6cd8ddbf004d40f520f8ee34d430dbae841
Timestamp: 1702671742 Timestamp [UCT]: 2023-12-15 20:22:22 Age [y:d:h:m:s]: 01:152:10:11:36
Block: 913893 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 370100 RingCT/type: yes/0
Extra: 0179d5207a0408ae4d5480aaee961fd6cd8ddbf004d40f520f8ee34d430dbae84102110000000d75e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 410d6db3011ce8a9a21d676233b4c2a93a44d65d252fa277e8816d0da3a8d292 0.600000000000 1371173 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": 913903, "vin": [ { "gen": { "height": 913893 } } ], "vout": [ { "amount": 600000000, "target": { "key": "410d6db3011ce8a9a21d676233b4c2a93a44d65d252fa277e8816d0da3a8d292" } } ], "extra": [ 1, 121, 213, 32, 122, 4, 8, 174, 77, 84, 128, 170, 238, 150, 31, 214, 205, 141, 219, 240, 4, 212, 15, 82, 15, 142, 227, 77, 67, 13, 186, 232, 65, 2, 17, 0, 0, 0, 13, 117, 227, 240, 233, 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