Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c4dc978098e2f40f25e073c882d632bbd7151b701264e29b09fb002a3762978

Tx prefix hash: ae182d419172478a91461ae62ad92bcabe0c1cd925d71553b8bfeaaa14100f70
Tx public key: 6df9ed6f91a559d3b5f8786016df3226a3b55a2a07ace5e46531e09fe3c50787
Timestamp: 1749360341 Timestamp [UCT]: 2025-06-08 05:25:41 Age [y:d:h:m:s]: 00:159:03:24:49
Block: 1300416 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111424 RingCT/type: yes/0
Extra: 016df9ed6f91a559d3b5f8786016df3226a3b55a2a07ace5e46531e09fe3c50787021100000004bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 254f760c6a29ec8199787816c744bda0c61cfb098d3c0394545fef537fb5b51d 0.600000000000 1787965 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": 1300426, "vin": [ { "gen": { "height": 1300416 } } ], "vout": [ { "amount": 600000000, "target": { "key": "254f760c6a29ec8199787816c744bda0c61cfb098d3c0394545fef537fb5b51d" } } ], "extra": [ 1, 109, 249, 237, 111, 145, 165, 89, 211, 181, 248, 120, 96, 22, 223, 50, 38, 163, 181, 90, 42, 7, 172, 229, 228, 101, 49, 224, 159, 227, 197, 7, 135, 2, 17, 0, 0, 0, 4, 191, 81, 178, 162, 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