Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 31f826cc526c4324f0adbb5fb01f812ecfe94d56f4fd742ab6dfaab0bfa6eca2

Tx prefix hash: daf7e243bba5c470eb451b1e769c1c85bac85b5de8bb7a7bb544376be84d1027
Tx public key: 1b67dab903a7f6c611ba45f8c8bf3b6c6de3e201f0a23c242a881f5434dc6d37
Timestamp: 1721271609 Timestamp [UCT]: 2024-07-18 03:00:09 Age [y:d:h:m:s]: 00:261:17:23:17
Block: 1068113 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186955 RingCT/type: yes/0
Extra: 011b67dab903a7f6c611ba45f8c8bf3b6c6de3e201f0a23c242a881f5434dc6d3702110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 80bd43e2234a2c0e946bfc57be4de3e1de9dd09e28dd503403541822a3f3234c 0.600000000000 1539132 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": 1068123, "vin": [ { "gen": { "height": 1068113 } } ], "vout": [ { "amount": 600000000, "target": { "key": "80bd43e2234a2c0e946bfc57be4de3e1de9dd09e28dd503403541822a3f3234c" } } ], "extra": [ 1, 27, 103, 218, 185, 3, 167, 246, 198, 17, 186, 69, 248, 200, 191, 59, 108, 109, 227, 226, 1, 240, 162, 60, 36, 42, 136, 31, 84, 52, 220, 109, 55, 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