Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7feba889343ec46e7cb147609af31193d75b6dc452dd4b6ac3fad5b44b8352ae

Tx prefix hash: b70272f022aeb5c398d9d812c63f2685201da563996dd302e1fdbd693445efcb
Tx public key: 2082cdba0d341fd30ebf73f3efaae97485ce4dd692b33f5b283da3fd56c66514
Timestamp: 1753423266 Timestamp [UCT]: 2025-07-25 06:01:06 Age [y:d:h:m:s]: 00:119:15:18:29
Block: 1332888 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84326 RingCT/type: yes/0
Extra: 012082cdba0d341fd30ebf73f3efaae97485ce4dd692b33f5b283da3fd56c6651402110000000201491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5e2b34b327b97b32ba43ab6a231ff1d9c3ef75ae507966cf5d7eaa97262a9535 0.600000000000 1820687 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": 1332898, "vin": [ { "gen": { "height": 1332888 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5e2b34b327b97b32ba43ab6a231ff1d9c3ef75ae507966cf5d7eaa97262a9535" } } ], "extra": [ 1, 32, 130, 205, 186, 13, 52, 31, 211, 14, 191, 115, 243, 239, 170, 233, 116, 133, 206, 77, 214, 146, 179, 63, 91, 40, 61, 163, 253, 86, 198, 101, 20, 2, 17, 0, 0, 0, 2, 1, 73, 31, 136, 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