Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 55f27113d619356446c114bcb40d3f5001270d69f9e0ff5bbad27ff15b87c77f

Tx prefix hash: f281d1bd11b4d22d21b9f87aa1ba8e0604439f6ea814ddb6734ad1e012a52ba1
Tx public key: ea0e4b33a49737fff3b645ac28adc5234e0073e6e3eb0560cd166de1df1c12d7
Timestamp: 1745491934 Timestamp [UCT]: 2025-04-24 10:52:14 Age [y:d:h:m:s]: 00:284:03:38:15
Block: 1268383 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200729 RingCT/type: yes/0
Extra: 01ea0e4b33a49737fff3b645ac28adc5234e0073e6e3eb0560cd166de1df1c12d70211000000056c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 34de4b00908b797ad4a00d3cf19322d0ad27426339bad31fd6d2b7cf31df75cd 0.600000000000 1755612 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": 1268393, "vin": [ { "gen": { "height": 1268383 } } ], "vout": [ { "amount": 600000000, "target": { "key": "34de4b00908b797ad4a00d3cf19322d0ad27426339bad31fd6d2b7cf31df75cd" } } ], "extra": [ 1, 234, 14, 75, 51, 164, 151, 55, 255, 243, 182, 69, 172, 40, 173, 197, 35, 78, 0, 115, 230, 227, 235, 5, 96, 205, 22, 109, 225, 223, 28, 18, 215, 2, 17, 0, 0, 0, 5, 108, 152, 170, 61, 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