Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7daacb0031d19e76f0bc5512fb78295470a1d59212aac6d08e721d67552e648e

Tx prefix hash: c06a54b52e85296dd7c09d584c4bef56c2f6f1862db65baf1221de120fce986d
Tx public key: e4a710e02733dd93c3eb2e1165fe8d1831dd732c8fb6a65998e86bb53bcc77c7
Timestamp: 1715520514 Timestamp [UCT]: 2024-05-12 13:28:34 Age [y:d:h:m:s]: 00:356:14:47:02
Block: 1020451 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 254882 RingCT/type: yes/0
Extra: 01e4a710e02733dd93c3eb2e1165fe8d1831dd732c8fb6a65998e86bb53bcc77c7021100000001c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2df979394230eb4e12b2059d376c1c2add921074d234832957b6cc037993ecf1 0.600000000000 1484524 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": 1020461, "vin": [ { "gen": { "height": 1020451 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2df979394230eb4e12b2059d376c1c2add921074d234832957b6cc037993ecf1" } } ], "extra": [ 1, 228, 167, 16, 224, 39, 51, 221, 147, 195, 235, 46, 17, 101, 254, 141, 24, 49, 221, 115, 44, 143, 182, 166, 89, 152, 232, 107, 181, 59, 204, 119, 199, 2, 17, 0, 0, 0, 1, 197, 69, 41, 96, 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