Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 892d4898c5d6be33cfe81ff5622ea96d96b855765482fd950c13a55b85b2237f

Tx prefix hash: 2e63aa64b32ae62b42b2b376d32177ae2fc6f17afa7f8a75417a44a1e1095b2b
Tx public key: bedf7e34d4b484c521635e753fbf96ca75a5e3126cdd809da72fc727720c8dd1
Timestamp: 1760885907 Timestamp [UCT]: 2025-10-19 14:58:27 Age [y:d:h:m:s]: 00:039:15:27:22
Block: 1393423 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 28364 RingCT/type: yes/0
Extra: 01bedf7e34d4b484c521635e753fbf96ca75a5e3126cdd809da72fc727720c8dd102110000000825a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5ca8031a3c79aa08e3fded32941a298f944ad4ca0a495817e9dd26df9dc68330 0.600000000000 1881688 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": 1393433, "vin": [ { "gen": { "height": 1393423 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5ca8031a3c79aa08e3fded32941a298f944ad4ca0a495817e9dd26df9dc68330" } } ], "extra": [ 1, 190, 223, 126, 52, 212, 180, 132, 197, 33, 99, 94, 117, 63, 191, 150, 202, 117, 165, 227, 18, 108, 221, 128, 157, 167, 47, 199, 39, 114, 12, 141, 209, 2, 17, 0, 0, 0, 8, 37, 163, 90, 15, 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