Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 03d486a3fcfdd3b9c9d37a6f36ffa3c0c8f14c74446d3ca44b015af5920c9794

Tx prefix hash: 44f905a438c240d2b29cd6fb6b378180e6df12a339cf522326d9cce142183ee1
Tx public key: fae68b8af9b59b902aa06992c2d3247e155c0103477539a5cfaa8f0668eb97a8
Timestamp: 1700417645 Timestamp [UCT]: 2023-11-19 18:14:05 Age [y:d:h:m:s]: 01:100:19:24:51
Block: 895207 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 333196 RingCT/type: yes/0
Extra: 01fae68b8af9b59b902aa06992c2d3247e155c0103477539a5cfaa8f0668eb97a8021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.663449057000 dcy

stealth address amount amount idx
00: 96924ae26942564f18b23246085effacaad0302fce8109795fe6c746d65b1265 0.663449057000 1351430 of 0

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": 895217, "vin": [ { "gen": { "height": 895207 } } ], "vout": [ { "amount": 663449057, "target": { "key": "96924ae26942564f18b23246085effacaad0302fce8109795fe6c746d65b1265" } } ], "extra": [ 1, 250, 230, 139, 138, 249, 181, 155, 144, 42, 160, 105, 146, 194, 211, 36, 126, 21, 92, 1, 3, 71, 117, 57, 165, 207, 170, 143, 6, 104, 235, 151, 168, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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