Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b9298765359ab10a89c841c7abea01ca4a5ff6f034adbcbfce68350b8d209e0

Tx prefix hash: a810c20ed64b391477e2f74d514776d3db6bfe999ac797880324b7bf438aab7b
Tx public key: c3ec852a9c778ddf8b0b477f53822ab913ce8a56f8d9b75a5d33b6ec769c6f8f
Timestamp: 1734656789 Timestamp [UCT]: 2024-12-20 01:06:29 Age [y:d:h:m:s]: 00:102:09:23:47
Block: 1178977 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72934 RingCT/type: yes/0
Extra: 01c3ec852a9c778ddf8b0b477f53822ab913ce8a56f8d9b75a5d33b6ec769c6f8f0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 59432e997480ce8b9777757091cd943e11ab91b4be17f765470bb6aaa9941bd3 0.600000000000 1665368 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": 1178987, "vin": [ { "gen": { "height": 1178977 } } ], "vout": [ { "amount": 600000000, "target": { "key": "59432e997480ce8b9777757091cd943e11ab91b4be17f765470bb6aaa9941bd3" } } ], "extra": [ 1, 195, 236, 133, 42, 156, 119, 141, 223, 139, 11, 71, 127, 83, 130, 42, 185, 19, 206, 138, 86, 248, 217, 183, 90, 93, 51, 182, 236, 118, 156, 111, 143, 2, 17, 0, 0, 0, 3, 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