Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e365c7926e389473eace391e9e24d7bacc5661ea4095e5646bee86433651f5d0

Tx prefix hash: 9e245ccbcfd354f7061b5bd8dfc6b4d9030c5b58ec1fe46650f31f47d67b9420
Tx public key: 142bc06b3f0ea7f4f0c587333b7ed1f214aaf0ad65eed8ab1cdfeae967c2cf96
Timestamp: 1734518863 Timestamp [UCT]: 2024-12-18 10:47:43 Age [y:d:h:m:s]: 00:104:04:55:36
Block: 1177842 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74223 RingCT/type: yes/0
Extra: 01142bc06b3f0ea7f4f0c587333b7ed1f214aaf0ad65eed8ab1cdfeae967c2cf960211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7d421eeffaad6387db8e46d34e07afb1426870ce80e76e01d2a772bdb9dcdb55 0.600000000000 1664219 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": 1177852, "vin": [ { "gen": { "height": 1177842 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7d421eeffaad6387db8e46d34e07afb1426870ce80e76e01d2a772bdb9dcdb55" } } ], "extra": [ 1, 20, 43, 192, 107, 63, 14, 167, 244, 240, 197, 135, 51, 59, 126, 209, 242, 20, 170, 240, 173, 101, 238, 216, 171, 28, 223, 234, 233, 103, 194, 207, 150, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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