Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 72f9ba4ddf45a04787e87f8a9e5371f7a3a6c0405d2146b6122d6968ec482052

Tx prefix hash: b691bfa29139e4e4adc9cf27b06ca46c3c388694727ef6f2989d62eb0ccc9d1e
Tx public key: 939c8f7218e665813dbdfaa781f696eec9d92d91f9eb099bc50f21e80093a88e
Timestamp: 1720186958 Timestamp [UCT]: 2024-07-05 13:42:38 Age [y:d:h:m:s]: 00:315:23:57:16
Block: 1059097 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 225825 RingCT/type: yes/0
Extra: 01939c8f7218e665813dbdfaa781f696eec9d92d91f9eb099bc50f21e80093a88e0211000000097a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3e31665f3c9a7842bbd4b5a35e8cd08a294657414f0b8edf644260efe3a865fa 0.600000000000 1529558 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": 1059107, "vin": [ { "gen": { "height": 1059097 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3e31665f3c9a7842bbd4b5a35e8cd08a294657414f0b8edf644260efe3a865fa" } } ], "extra": [ 1, 147, 156, 143, 114, 24, 230, 101, 129, 61, 189, 250, 167, 129, 246, 150, 238, 201, 217, 45, 145, 249, 235, 9, 155, 197, 15, 33, 232, 0, 147, 168, 142, 2, 17, 0, 0, 0, 9, 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