Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 468f725042e507e3362cd0f30d007167a99ed8f3bda8c20afc17c784d3d12235

Tx prefix hash: db7d251b1973df31074f32c8ed9cde4833aa6448c81dc4079822aa5d998ce694
Tx public key: 9fa2ffa26cea1d63fbeb1c72e1a85f2c1af0d983aec8f51889d8a1e0f0e71df1
Timestamp: 1761719424 Timestamp [UCT]: 2025-10-29 06:30:24 Age [y:d:h:m:s]: 00:053:18:27:56
Block: 1400324 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 38484 RingCT/type: yes/0
Extra: 019fa2ffa26cea1d63fbeb1c72e1a85f2c1af0d983aec8f51889d8a1e0f0e71df1021100000002df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 778028212a56b25cfe8d9caeeaa6d7388dc8c179965c095f8e2f681365413d01 0.600000000000 1888631 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": 1400334, "vin": [ { "gen": { "height": 1400324 } } ], "vout": [ { "amount": 600000000, "target": { "key": "778028212a56b25cfe8d9caeeaa6d7388dc8c179965c095f8e2f681365413d01" } } ], "extra": [ 1, 159, 162, 255, 162, 108, 234, 29, 99, 251, 235, 28, 114, 225, 168, 95, 44, 26, 240, 217, 131, 174, 200, 245, 24, 137, 216, 161, 224, 240, 231, 29, 241, 2, 17, 0, 0, 0, 2, 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