Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f220e1f9ba2158857d49b5ca5f688c32168b32a271e087c286624f2aba69995a

Tx prefix hash: 05759b6060aef7d92d3f26ab94c1c7e18b441013aadcc7f06dccefd7a95236ce
Tx public key: 1c85de3ad0e6e674559fdc4f3a47563a4dd583be193db3be119b152c04d5325a
Timestamp: 1764307861 Timestamp [UCT]: 2025-11-28 05:31:01 Age [y:d:h:m:s]: 00:025:17:18:31
Block: 1421758 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 18406 RingCT/type: yes/0
Extra: 011c85de3ad0e6e674559fdc4f3a47563a4dd583be193db3be119b152c04d5325a0211000000014e7bfc09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8d9f3af73055ca2bceaac6258704e69d215cc58cf5024184bdf65bb1a28a0458 0.600000000000 1910315 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": 1421768, "vin": [ { "gen": { "height": 1421758 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8d9f3af73055ca2bceaac6258704e69d215cc58cf5024184bdf65bb1a28a0458" } } ], "extra": [ 1, 28, 133, 222, 58, 208, 230, 230, 116, 85, 159, 220, 79, 58, 71, 86, 58, 77, 213, 131, 190, 25, 61, 179, 190, 17, 155, 21, 44, 4, 213, 50, 90, 2, 17, 0, 0, 0, 1, 78, 123, 252, 9, 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