Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e3015523aa1d26f0491bc212d1988e9d330423d3c0df749accf4ee7c050d7921

Tx prefix hash: efe8aa34d8d519b3e72af90f5e3b2181210da8d34885e832e9be946eb780676b
Tx public key: c85b0f17f3ab4badfd7dd02546b08c6d874a6c10aacc5f91b765d19b30ea4ee5
Timestamp: 1708259924 Timestamp [UCT]: 2024-02-18 12:38:44 Age [y:d:h:m:s]: 01:277:01:30:26
Block: 960229 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 456766 RingCT/type: yes/0
Extra: 01c85b0f17f3ab4badfd7dd02546b08c6d874a6c10aacc5f91b765d19b30ea4ee50211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f493da07459d4c912ad7f762a789ee8eb22a882f614bcd5fbf38e0525e9b346e 0.600000000000 1419792 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": 960239, "vin": [ { "gen": { "height": 960229 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f493da07459d4c912ad7f762a789ee8eb22a882f614bcd5fbf38e0525e9b346e" } } ], "extra": [ 1, 200, 91, 15, 23, 243, 171, 75, 173, 253, 125, 208, 37, 70, 176, 140, 109, 135, 74, 108, 16, 170, 204, 95, 145, 183, 101, 209, 155, 48, 234, 78, 229, 2, 17, 0, 0, 0, 7, 122, 156, 244, 199, 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