Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7200bb7edaf441aace89ab2fd1bcb5ebb55fe8c3e2d13669de9970d2706909a

Tx prefix hash: 7175f9dc5daf9626cd0070fd818ea5a647183e009dc1447df1951494596157fb
Tx public key: b6faaa9ae6e2a5f8c7dfcc80719fd4d3b4c3120a8b3abf6ffbd33345b8f6af2a
Timestamp: 1670389117 Timestamp [UCT]: 2022-12-07 04:58:37 Age [y:d:h:m:s]: 02:335:11:56:32
Block: 647149 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 759185 RingCT/type: yes/0
Extra: 01b6faaa9ae6e2a5f8c7dfcc80719fd4d3b4c3120a8b3abf6ffbd33345b8f6af2a02110000000183600029000000000000000000

1 output(s) for total of 4.402777206000 dcy

stealth address amount amount idx
00: f1f3708a2b700afdce915f74111251f1e1341d46dc3497648192a831b216f262 4.402777206000 1087406 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": 647159, "vin": [ { "gen": { "height": 647149 } } ], "vout": [ { "amount": 4402777206, "target": { "key": "f1f3708a2b700afdce915f74111251f1e1341d46dc3497648192a831b216f262" } } ], "extra": [ 1, 182, 250, 170, 154, 230, 226, 165, 248, 199, 223, 204, 128, 113, 159, 212, 211, 180, 195, 18, 10, 139, 58, 191, 111, 251, 211, 51, 69, 184, 246, 175, 42, 2, 17, 0, 0, 0, 1, 131, 96, 0, 41, 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