Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 92ed1b55e0917997ea6cb509e3ab044a4acbdd17b12e09b4ec7dd78455a91187

Tx prefix hash: ebcbc49bb50168da2eb9768ef00b57bc313590d47d890ec4ceb0a583d5bdd315
Tx public key: 66df59fdc89bccb2e04c80f3d62f0772550411cf5a930cc267d92d9f4feba12a
Timestamp: 1764886939 Timestamp [UCT]: 2025-12-04 22:22:19 Age [y:d:h:m:s]: 00:034:20:07:30
Block: 1426576 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 24933 RingCT/type: yes/0
Extra: 0166df59fdc89bccb2e04c80f3d62f0772550411cf5a930cc267d92d9f4feba12a02110000000ad6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a25bf8172611bc34763e892434af44b560936b90c99eabf8ec8d29084ce7e86d 0.600000000000 1915269 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": 1426586, "vin": [ { "gen": { "height": 1426576 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a25bf8172611bc34763e892434af44b560936b90c99eabf8ec8d29084ce7e86d" } } ], "extra": [ 1, 102, 223, 89, 253, 200, 155, 204, 178, 224, 76, 128, 243, 214, 47, 7, 114, 85, 4, 17, 207, 90, 147, 12, 194, 103, 217, 45, 159, 79, 235, 161, 42, 2, 17, 0, 0, 0, 10, 214, 225, 157, 124, 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