Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e01bce3227bc5100ca18e2a67ede037c2c4b7c28ac333d88fbf5a5e37ca74bad

Tx prefix hash: 1a2e373dc7ffb32773e75de976681eb3177764c32e061716e4cef3ad91b78c5c
Tx public key: 74ab999a3f58de3bb0f6c38951a847043f19b3cdb593b54f4c7db3cb42157fa6
Timestamp: 1705344086 Timestamp [UCT]: 2024-01-15 18:41:26 Age [y:d:h:m:s]: 01:008:05:20:17
Block: 936029 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 267168 RingCT/type: yes/0
Extra: 0174ab999a3f58de3bb0f6c38951a847043f19b3cdb593b54f4c7db3cb42157fa602110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f285aab5f88563fb299bd27d737d2fa486f0a9f3abe710b063579688700cb68c 0.600000000000 1394051 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": 936039, "vin": [ { "gen": { "height": 936029 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f285aab5f88563fb299bd27d737d2fa486f0a9f3abe710b063579688700cb68c" } } ], "extra": [ 1, 116, 171, 153, 154, 63, 88, 222, 59, 176, 246, 195, 137, 81, 168, 71, 4, 63, 25, 179, 205, 181, 147, 181, 79, 76, 125, 179, 203, 66, 21, 127, 166, 2, 17, 0, 0, 0, 5, 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