Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 78b11842f1037bfe379dcbd0b084a8d484dbb099098de30cfd69a89ac30c2fa7

Tx prefix hash: 968577f49f3bcdf8962df06188b0ce5e4eb3c248899c94029f58a683e6666cca
Tx public key: 9e55bb6aa505e8b58edf68063445dc71601e2ef208841f8d78c880f09d8e0777
Timestamp: 1766177997 Timestamp [UCT]: 2025-12-19 20:59:57 Age [y:d:h:m:s]: 00:002:13:45:27
Block: 1437263 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1834 RingCT/type: yes/0
Extra: 019e55bb6aa505e8b58edf68063445dc71601e2ef208841f8d78c880f09d8e077702110000000470609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 35f6b34fc2c8a3d85b2ea6c79170c9e4c054eb94ecca177e0a2b6ed40c8c92d8 0.600000000000 1926070 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": 1437273, "vin": [ { "gen": { "height": 1437263 } } ], "vout": [ { "amount": 600000000, "target": { "key": "35f6b34fc2c8a3d85b2ea6c79170c9e4c054eb94ecca177e0a2b6ed40c8c92d8" } } ], "extra": [ 1, 158, 85, 187, 106, 165, 5, 232, 181, 142, 223, 104, 6, 52, 69, 220, 113, 96, 30, 46, 242, 8, 132, 31, 141, 120, 200, 128, 240, 157, 142, 7, 119, 2, 17, 0, 0, 0, 4, 112, 96, 157, 3, 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