Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 970b25856a7a9c409259ca4959bab2fd0b0d8b6cb641e3f18735a6846d43f628

Tx prefix hash: 95759d6082d5b664554f464b43b5c5105d5f37912ec641b84b2c4c781e7dc921
Tx public key: 28ab2ca1aa01c1a5330ce5f4c72ca632dac45374ac15c83cbf5b4edeb84258d5
Timestamp: 1753439076 Timestamp [UCT]: 2025-07-25 10:24:36 Age [y:d:h:m:s]: 00:025:09:39:21
Block: 1333012 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 17075 RingCT/type: yes/0
Extra: 0128ab2ca1aa01c1a5330ce5f4c72ca632dac45374ac15c83cbf5b4edeb84258d5021100000009ef221485000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6bfaf07ee97c0d79c9c50684cbd6fe9ff2bc8ea678863613398116fbc18dfae5 0.600000000000 1820811 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": 1333022, "vin": [ { "gen": { "height": 1333012 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6bfaf07ee97c0d79c9c50684cbd6fe9ff2bc8ea678863613398116fbc18dfae5" } } ], "extra": [ 1, 40, 171, 44, 161, 170, 1, 193, 165, 51, 12, 229, 244, 199, 44, 166, 50, 218, 196, 83, 116, 172, 21, 200, 60, 191, 91, 78, 222, 184, 66, 88, 213, 2, 17, 0, 0, 0, 9, 239, 34, 20, 133, 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