Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11d1b98a64f035798932c797c040469a1ae7e8e29309b529006f24a3194cf80e

Tx prefix hash: 5a8381aac1bf39af802e09d106124d709dca1e0115a0467ceb37d54348fa9a3c
Tx public key: 9ef4f9eed3de2a4149d71edce1a76c9e0eab11670ebb9fd03adf970b8960cfe0
Timestamp: 1701486519 Timestamp [UCT]: 2023-12-02 03:08:39 Age [y:d:h:m:s]: 01:151:02:26:04
Block: 904059 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 369158 RingCT/type: yes/0
Extra: 019ef4f9eed3de2a4149d71edce1a76c9e0eab11670ebb9fd03adf970b8960cfe0021100000001e08532b6000000000000000000

1 output(s) for total of 0.620122112000 dcy

stealth address amount amount idx
00: 9906c3bb64a9e2eb7b14c200978697123ffd66daa04ce5b8643d3c41044a3373 0.620122112000 1360762 of 0

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": 904069, "vin": [ { "gen": { "height": 904059 } } ], "vout": [ { "amount": 620122112, "target": { "key": "9906c3bb64a9e2eb7b14c200978697123ffd66daa04ce5b8643d3c41044a3373" } } ], "extra": [ 1, 158, 244, 249, 238, 211, 222, 42, 65, 73, 215, 30, 220, 225, 167, 108, 158, 14, 171, 17, 103, 14, 187, 159, 208, 58, 223, 151, 11, 137, 96, 207, 224, 2, 17, 0, 0, 0, 1, 224, 133, 50, 182, 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