Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 83f272a4b874e4f138d15945cb76c3d8042bfba5703d19c4dc16b87bab17f386

Tx prefix hash: 4243ca943f61519d10f4073445167cc073b2e4a771bbe97608f2da38635c8c23
Tx public key: 8e01aae20de25234fec5002924a076fbb3d7a79175584bcbc7c16a9fa7ae8ee3
Timestamp: 1708011908 Timestamp [UCT]: 2024-02-15 15:45:08 Age [y:d:h:m:s]: 01:009:18:35:33
Block: 958159 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 267997 RingCT/type: yes/0
Extra: 018e01aae20de25234fec5002924a076fbb3d7a79175584bcbc7c16a9fa7ae8ee302110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9b2e41e30064be6fb710aa19a2838803090d7f3d75519cd9daa59d68bcbca81b 0.600000000000 1417512 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": 958169, "vin": [ { "gen": { "height": 958159 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9b2e41e30064be6fb710aa19a2838803090d7f3d75519cd9daa59d68bcbca81b" } } ], "extra": [ 1, 142, 1, 170, 226, 13, 226, 82, 52, 254, 197, 0, 41, 36, 160, 118, 251, 179, 215, 167, 145, 117, 88, 75, 203, 199, 193, 106, 159, 167, 174, 142, 227, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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