Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c9f20d3a52b8a7b96903f62d11a1aa59883e8af65f97710339949aa0c5c6a58

Tx prefix hash: fd172042f49f28f421bf6c263a5643937ee5bce127bace6415a69566cf9f0121
Tx public key: f84ea4caf827d56251c97bf7dc735d510510162ea4fbdea431cc39962c36ef4a
Timestamp: 1617105983 Timestamp [UCT]: 2021-03-30 12:06:23 Age [y:d:h:m:s]: 04:014:19:41:43
Block: 229686 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1030734 RingCT/type: yes/0
Extra: 01f84ea4caf827d56251c97bf7dc735d510510162ea4fbdea431cc39962c36ef4a0211000000790dc70aa7000000000000000000

1 output(s) for total of 106.411932768000 dcy

stealth address amount amount idx
00: 4f2ed1cfd0cfdfe4c625d3e686135f9c2ead0f89c591870162a17629602caceb 106.411932768000 476658 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": 229696, "vin": [ { "gen": { "height": 229686 } } ], "vout": [ { "amount": 106411932768, "target": { "key": "4f2ed1cfd0cfdfe4c625d3e686135f9c2ead0f89c591870162a17629602caceb" } } ], "extra": [ 1, 248, 78, 164, 202, 248, 39, 213, 98, 81, 201, 123, 247, 220, 115, 93, 81, 5, 16, 22, 46, 164, 251, 222, 164, 49, 204, 57, 150, 44, 54, 239, 74, 2, 17, 0, 0, 0, 121, 13, 199, 10, 167, 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