Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f01e4e926d0ab69056a36f8cb06beaa995ac9b85da399c339705ad65b9f334e3

Tx prefix hash: 65a93414bdabe952ab4f085e769f505ea86dec6bc545f2f7a69129cd31b9a1e6
Tx public key: 065a026419c0d2fafe44d9f11e48b6a1330a50ef6fb48dd97ce74f9fdbe40343
Timestamp: 1700175787 Timestamp [UCT]: 2023-11-16 23:03:07 Age [y:d:h:m:s]: 01:137:04:04:38
Block: 893209 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 359190 RingCT/type: yes/0
Extra: 01065a026419c0d2fafe44d9f11e48b6a1330a50ef6fb48dd97ce74f9fdbe40343021100000001adb802c3000000000000000000

1 output(s) for total of 0.673639877000 dcy

stealth address amount amount idx
00: bf261ef354867edb3b91e208f0189362c6e8ebedc9af3d39c0d5802215b65690 0.673639877000 1349372 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": 893219, "vin": [ { "gen": { "height": 893209 } } ], "vout": [ { "amount": 673639877, "target": { "key": "bf261ef354867edb3b91e208f0189362c6e8ebedc9af3d39c0d5802215b65690" } } ], "extra": [ 1, 6, 90, 2, 100, 25, 192, 210, 250, 254, 68, 217, 241, 30, 72, 182, 161, 51, 10, 80, 239, 111, 180, 141, 217, 124, 231, 79, 159, 219, 228, 3, 67, 2, 17, 0, 0, 0, 1, 173, 184, 2, 195, 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