Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 252331c01c5b9bba324910cd41ab780f9f511ca5f3a226547d29a169d73faa48

Tx prefix hash: e792405c08130569fd26caaf761712e8c3bff5d534590d46bb08f0897a9fdd20
Tx public key: bac7c9d7284a6ebf92a9e028aa2cfa9beb40895389ad5b3a2cf6a5ce40beeef3
Timestamp: 1760986082 Timestamp [UCT]: 2025-10-20 18:48:02 Age [y:d:h:m:s]: 00:101:14:16:23
Block: 1394257 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72547 RingCT/type: yes/0
Extra: 01bac7c9d7284a6ebf92a9e028aa2cfa9beb40895389ad5b3a2cf6a5ce40beeef302110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9e1635444439d61f741f96b78e9dd119d788bc32d264b7a6223ee87baa86f3fd 0.600000000000 1882528 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": 1394267, "vin": [ { "gen": { "height": 1394257 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9e1635444439d61f741f96b78e9dd119d788bc32d264b7a6223ee87baa86f3fd" } } ], "extra": [ 1, 186, 199, 201, 215, 40, 74, 110, 191, 146, 169, 224, 40, 170, 44, 250, 155, 235, 64, 137, 83, 137, 173, 91, 58, 44, 246, 165, 206, 64, 190, 238, 243, 2, 17, 0, 0, 0, 1, 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