Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 12f2698a36b39b5280f051a85b0a6ea362f63a56adc1ebd21318c1e0f4f6907f

Tx prefix hash: 16b220e5d134cb86a50f780dba782bfb67915a28f67b5bc427887e8c21f80894
Tx public key: b91c83d4fab5b2eb9765390fc1275ffc185916a5f5b7ed16479d224b66713642
Timestamp: 1726373714 Timestamp [UCT]: 2024-09-15 04:15:14 Age [y:d:h:m:s]: 00:240:22:48:08
Block: 1110394 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172068 RingCT/type: yes/0
Extra: 01b91c83d4fab5b2eb9765390fc1275ffc185916a5f5b7ed16479d224b66713642021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 31b5f6134a556a657276a8eef7b22620c30e3b74da9e2173d87ed853b29861f5 0.600000000000 1588987 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": 1110404, "vin": [ { "gen": { "height": 1110394 } } ], "vout": [ { "amount": 600000000, "target": { "key": "31b5f6134a556a657276a8eef7b22620c30e3b74da9e2173d87ed853b29861f5" } } ], "extra": [ 1, 185, 28, 131, 212, 250, 181, 178, 235, 151, 101, 57, 15, 193, 39, 95, 252, 24, 89, 22, 165, 245, 183, 237, 22, 71, 157, 34, 75, 102, 113, 54, 66, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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