Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c0fa78f24fb08ec598c091a7c1f9991d8eca02461409a406f3f01fa56cbd2be

Tx prefix hash: ba19d9a27ae62a178e954781fe0348cb2f38ac0baa87a2ebb5236ad462ac3fce
Tx public key: a24a0df0c7cc044d1436c70dbbcd9b20d802529b0a7225a7b1b9a890495cdced
Timestamp: 1762342017 Timestamp [UCT]: 2025-11-05 11:26:57 Age [y:d:h:m:s]: 00:085:16:21:44
Block: 1405458 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 61181 RingCT/type: yes/0
Extra: 01a24a0df0c7cc044d1436c70dbbcd9b20d802529b0a7225a7b1b9a890495cdced02110000000adf5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 680a11b56cac86a1165a6f82ccbd00e96211cbc623fa90ae2644cd5ddb57b851 0.600000000000 1893829 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": 1405468, "vin": [ { "gen": { "height": 1405458 } } ], "vout": [ { "amount": 600000000, "target": { "key": "680a11b56cac86a1165a6f82ccbd00e96211cbc623fa90ae2644cd5ddb57b851" } } ], "extra": [ 1, 162, 74, 13, 240, 199, 204, 4, 77, 20, 54, 199, 13, 187, 205, 155, 32, 216, 2, 82, 155, 10, 114, 37, 167, 177, 185, 168, 144, 73, 92, 220, 237, 2, 17, 0, 0, 0, 10, 223, 90, 36, 122, 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