Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d2b33c40dd8faae32361f6bbcc3e305b67840ed919ba676322927312217b2dd

Tx prefix hash: 7f8222b5f360089802e8747d5a7c0f79992de079abf679305b9a6a823aca97ba
Tx public key: e47003c68d2ae5c73412f79569851ccb613fe2cc3a95890d5e6e46e1ce529b0a
Timestamp: 1738069513 Timestamp [UCT]: 2025-01-28 13:05:13 Age [y:d:h:m:s]: 00:146:18:38:26
Block: 1206948 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104716 RingCT/type: yes/0
Extra: 01e47003c68d2ae5c73412f79569851ccb613fe2cc3a95890d5e6e46e1ce529b0a021100000002dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 35daa76f16a6a06b39c8a2e6e89abb94e4e35aa86e842903c0b64cb666442ef4 0.600000000000 1693667 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": 1206958, "vin": [ { "gen": { "height": 1206948 } } ], "vout": [ { "amount": 600000000, "target": { "key": "35daa76f16a6a06b39c8a2e6e89abb94e4e35aa86e842903c0b64cb666442ef4" } } ], "extra": [ 1, 228, 112, 3, 198, 141, 42, 229, 199, 52, 18, 247, 149, 105, 133, 28, 203, 97, 63, 226, 204, 58, 149, 137, 13, 94, 110, 70, 225, 206, 82, 155, 10, 2, 17, 0, 0, 0, 2, 223, 195, 186, 73, 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