Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 61d64d6e22a14c143646045c1fcc6528c99216bb82eef48aeac3f7198de94f85

Tx prefix hash: d780ca3804bb6a0d29279471c716c7c07584efbc2465e9abf44a0071cc413dec
Tx public key: c3fbe706d7756ce8d72be03e81bad82b8f129d0b6bdca6a821c7aaaaf4154f9f
Timestamp: 1703865903 Timestamp [UCT]: 2023-12-29 16:05:03 Age [y:d:h:m:s]: 01:099:05:50:53
Block: 923805 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 332018 RingCT/type: yes/0
Extra: 01c3fbe706d7756ce8d72be03e81bad82b8f129d0b6bdca6a821c7aaaaf4154f9f0211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 786f6c2e48ab717f538e39d60a89e96b69aff83c4c339cb8149627368c3f94f0 0.600000000000 1381541 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": 923815, "vin": [ { "gen": { "height": 923805 } } ], "vout": [ { "amount": 600000000, "target": { "key": "786f6c2e48ab717f538e39d60a89e96b69aff83c4c339cb8149627368c3f94f0" } } ], "extra": [ 1, 195, 251, 231, 6, 215, 117, 108, 232, 215, 43, 224, 62, 129, 186, 216, 43, 143, 18, 157, 11, 107, 220, 166, 168, 33, 199, 170, 170, 244, 21, 79, 159, 2, 17, 0, 0, 0, 7, 122, 156, 244, 199, 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