Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8afc2d00cfa79fdfc3cc79db01af28f1cd2031506d224800e39e3c67b07030ff

Tx prefix hash: 449f596d7353909e3aa0c2483d124392a80d6e9829c1c5a61c28d7966110480d
Tx public key: 62ce0bee59e792504ae091f6055ca917e5aaa335db2ef3a0aa4c25d08589a057
Timestamp: 1724161144 Timestamp [UCT]: 2024-08-20 13:39:04 Age [y:d:h:m:s]: 00:253:00:26:47
Block: 1092055 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180714 RingCT/type: yes/0
Extra: 0162ce0bee59e792504ae091f6055ca917e5aaa335db2ef3a0aa4c25d08589a05702110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb463e16b9f74908e6bfb53fbebb3fc28bad8cd0b954992082c2749ab6e77ca7 0.600000000000 1566726 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": 1092065, "vin": [ { "gen": { "height": 1092055 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb463e16b9f74908e6bfb53fbebb3fc28bad8cd0b954992082c2749ab6e77ca7" } } ], "extra": [ 1, 98, 206, 11, 238, 89, 231, 146, 80, 74, 224, 145, 246, 5, 92, 169, 23, 229, 170, 163, 53, 219, 46, 243, 160, 170, 76, 37, 208, 133, 137, 160, 87, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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