Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c18e0e2beaceeed83883ae911aac3a39ff92a604b3165e68798f9a37f7d7cea9

Tx prefix hash: 3496da2ee1c7adb8f6b3b5ccb85d80eb425c39f7851f85897158091309a39fd8
Tx public key: 00e0286fee5261c04172c69a12c9e909055fd9b72b1e791945de410ded729174
Timestamp: 1582991733 Timestamp [UCT]: 2020-02-29 15:55:33 Age [y:d:h:m:s]: 05:001:18:16:55
Block: 74235 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1155495 RingCT/type: yes/0
Extra: 0100e0286fee5261c04172c69a12c9e909055fd9b72b1e791945de410ded7291740211000000a07adf42d3000000000000000000

1 output(s) for total of 348.360918518000 dcy

stealth address amount amount idx
00: a9bfc2350faca500eace17b27eb5a98c8d7c308ea3cdb245156363639a256d8c 348.360918518000 137265 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": 74245, "vin": [ { "gen": { "height": 74235 } } ], "vout": [ { "amount": 348360918518, "target": { "key": "a9bfc2350faca500eace17b27eb5a98c8d7c308ea3cdb245156363639a256d8c" } } ], "extra": [ 1, 0, 224, 40, 111, 238, 82, 97, 192, 65, 114, 198, 154, 18, 201, 233, 9, 5, 95, 217, 183, 43, 30, 121, 25, 69, 222, 65, 13, 237, 114, 145, 116, 2, 17, 0, 0, 0, 160, 122, 223, 66, 211, 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