Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81aa0e11cfa14b9b10e63c8c6a527129a46bd9ac317141763723779be81f0e5d

Tx prefix hash: 6e8938e3b2c8702ff1d72830dce01c0559898f04713d6fb6b7e7213225044115
Tx public key: e06ff7c45d7f8fed42a9854d9d2c0f36b97013bb4054416981574c6b1be6c26a
Timestamp: 1716284007 Timestamp [UCT]: 2024-05-21 09:33:27 Age [y:d:h:m:s]: 00:191:17:14:03
Block: 1026764 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 137210 RingCT/type: yes/0
Extra: 01e06ff7c45d7f8fed42a9854d9d2c0f36b97013bb4054416981574c6b1be6c26a02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0dcabb93ff4186fe1571a234d775738499a8aac406df8e5db5e12a938a490cee 0.600000000000 1494019 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": 1026774, "vin": [ { "gen": { "height": 1026764 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0dcabb93ff4186fe1571a234d775738499a8aac406df8e5db5e12a938a490cee" } } ], "extra": [ 1, 224, 111, 247, 196, 93, 127, 143, 237, 66, 169, 133, 77, 157, 44, 15, 54, 185, 112, 19, 187, 64, 84, 65, 105, 129, 87, 76, 107, 27, 230, 194, 106, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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