Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d96c53bf21fac644b846629f3e1fd1df5edede458a09b047c319db6589e9c3e

Tx prefix hash: e92ecf7b48bb530a7123eb9e9774a263b9f1efc29aa01a12f5967b5bd72dcd42
Tx public key: 1e9f223ea14d22a9e94781c6d89ea0dd2cc9c1eb8eccdf3377dc6bcb389e25d1
Timestamp: 1749489645 Timestamp [UCT]: 2025-06-09 17:20:45 Age [y:d:h:m:s]: 00:154:20:09:01
Block: 1301484 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108343 RingCT/type: yes/0
Extra: 011e9f223ea14d22a9e94781c6d89ea0dd2cc9c1eb8eccdf3377dc6bcb389e25d102110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a0ba33bdc85a963671302683bb686e29f8475a0e6be17950632a363d3a69b081 0.600000000000 1789043 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": 1301494, "vin": [ { "gen": { "height": 1301484 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0ba33bdc85a963671302683bb686e29f8475a0e6be17950632a363d3a69b081" } } ], "extra": [ 1, 30, 159, 34, 62, 161, 77, 34, 169, 233, 71, 129, 198, 216, 158, 160, 221, 44, 201, 193, 235, 142, 204, 223, 51, 119, 220, 107, 203, 56, 158, 37, 209, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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