Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2392c9aa61b6e2c90f1e8d9aa5c5babe2b6d729b8e8bb030ca9b8a516f901f5

Tx prefix hash: e00a97dff5f72e019f03fe2f66a767b1688e0b54a215af45cee77ace98b588e4
Tx public key: 73e2f2079f6637a62ad0e3dd2094e88bc1d10fe53fd5e3f72fa2e2261998fb08
Timestamp: 1634948473 Timestamp [UCT]: 2021-10-23 00:21:13 Age [y:d:h:m:s]: 03:066:13:23:27
Block: 358454 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 825877 RingCT/type: yes/0
Extra: 0173e2f2079f6637a62ad0e3dd2094e88bc1d10fe53fd5e3f72fa2e2261998fb0802110000000c3fc41461000000000000000000

1 output(s) for total of 39.837631301000 dcy

stealth address amount amount idx
00: 552aa9f057fed5e44411559afe3aa31f0246b79e3210c0cd3fe4260fef06515e 39.837631301000 730383 of 0

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": 358464, "vin": [ { "gen": { "height": 358454 } } ], "vout": [ { "amount": 39837631301, "target": { "key": "552aa9f057fed5e44411559afe3aa31f0246b79e3210c0cd3fe4260fef06515e" } } ], "extra": [ 1, 115, 226, 242, 7, 159, 102, 55, 166, 42, 208, 227, 221, 32, 148, 232, 139, 193, 209, 15, 229, 63, 213, 227, 247, 47, 162, 226, 38, 25, 152, 251, 8, 2, 17, 0, 0, 0, 12, 63, 196, 20, 97, 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