Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 55657ca267b7b1a31954f3058f9507d5e1567af309b04a7b406e0a0624ef0400

Tx prefix hash: da93b667ced29eac668ebc035f152429864dec5c5c79a4b2f9210023c72da0aa
Tx public key: eb446de84f3738e6612247781d0af3e14b616632808418d4a8c9f867d1c6e08b
Timestamp: 1762045171 Timestamp [UCT]: 2025-11-02 00:59:31 Age [y:d:h:m:s]: 00:004:21:16:03
Block: 1403005 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3500 RingCT/type: yes/0
Extra: 01eb446de84f3738e6612247781d0af3e14b616632808418d4a8c9f867d1c6e08b021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f0f129212cedfdf9008fd2bacd2b60d874df0e8b9d8479be6d4077228e44d4c6 0.600000000000 1891332 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": 1403015, "vin": [ { "gen": { "height": 1403005 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f0f129212cedfdf9008fd2bacd2b60d874df0e8b9d8479be6d4077228e44d4c6" } } ], "extra": [ 1, 235, 68, 109, 232, 79, 55, 56, 230, 97, 34, 71, 120, 29, 10, 243, 225, 75, 97, 102, 50, 128, 132, 24, 212, 168, 201, 248, 103, 209, 198, 224, 139, 2, 17, 0, 0, 0, 2, 228, 220, 144, 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