Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d0d16fe2f0018554a7cdd7fa36200f1fce12d9dda24e7e42ff8cedac6325f1b

Tx prefix hash: 252f0c158ab86ffe978cf98e3656f0a6630f2ad17f5680a560fadcc33f83b19d
Tx public key: 24f9a10f0508df7f037a79e87b638fe1fd2fcb108d7b56ae44ba1b2868a20420
Timestamp: 1720613647 Timestamp [UCT]: 2024-07-10 12:14:07 Age [y:d:h:m:s]: 00:112:05:19:07
Block: 1062648 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80302 RingCT/type: yes/0
Extra: 0124f9a10f0508df7f037a79e87b638fe1fd2fcb108d7b56ae44ba1b2868a2042002110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6c671a202d37aef4b7c83f0c25b1077a5516a1552542776feeee6ec1598df7d4 0.600000000000 1533153 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": 1062658, "vin": [ { "gen": { "height": 1062648 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6c671a202d37aef4b7c83f0c25b1077a5516a1552542776feeee6ec1598df7d4" } } ], "extra": [ 1, 36, 249, 161, 15, 5, 8, 223, 127, 3, 122, 121, 232, 123, 99, 143, 225, 253, 47, 203, 16, 141, 123, 86, 174, 68, 186, 27, 40, 104, 162, 4, 32, 2, 17, 0, 0, 0, 8, 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