Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 18e0534efd391002cc126d19537edc2553d22b5f721d3a6627932ae719826bdd

Tx prefix hash: 66e27a0be3ad23bf4ebe7895201eeb38dfb2ece884be4ff5578e06c7d40178fa
Tx public key: 7eb933b34bc5aed92a6aea14b18612c811c69908be2a0b196e568b34f4aa09ac
Timestamp: 1750292688 Timestamp [UCT]: 2025-06-19 00:24:48 Age [y:d:h:m:s]: 00:155:16:30:27
Block: 1308007 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109072 RingCT/type: yes/0
Extra: 017eb933b34bc5aed92a6aea14b18612c811c69908be2a0b196e568b34f4aa09ac02110000000543846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b694db517a986e1f59f218de406fdb6db551ffd919f137ba7947afaadfb7e219 0.600000000000 1795618 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": 1308017, "vin": [ { "gen": { "height": 1308007 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b694db517a986e1f59f218de406fdb6db551ffd919f137ba7947afaadfb7e219" } } ], "extra": [ 1, 126, 185, 51, 179, 75, 197, 174, 217, 42, 106, 234, 20, 177, 134, 18, 200, 17, 198, 153, 8, 190, 42, 11, 25, 110, 86, 139, 52, 244, 170, 9, 172, 2, 17, 0, 0, 0, 5, 67, 132, 109, 102, 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