Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2e2572ea369d77176c60940ee300e5b387bcd853f76ab185ff69350abb1933a

Tx prefix hash: d27dd3af4ce305e526d7af193885c767999c263b843669a45d6e059b4c56957c
Tx public key: 6d9b4da3b3202ace7ccdc527dfb3c2772d95b660d852ac460aad9466843ae9e5
Timestamp: 1583079163 Timestamp [UCT]: 2020-03-01 16:12:43 Age [y:d:h:m:s]: 04:299:10:45:30
Block: 74560 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1108036 RingCT/type: yes/0
Extra: 016d9b4da3b3202ace7ccdc527dfb3c2772d95b660d852ac460aad9466843ae9e50211000002b903d36d11000000000000000000

1 output(s) for total of 347.498205802000 dcy

stealth address amount amount idx
00: e3ec4a99e5b7fe72ae21476b30d4eb51b2e9da598a4537bbece7ef83f24b992c 347.498205802000 137966 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": 74570, "vin": [ { "gen": { "height": 74560 } } ], "vout": [ { "amount": 347498205802, "target": { "key": "e3ec4a99e5b7fe72ae21476b30d4eb51b2e9da598a4537bbece7ef83f24b992c" } } ], "extra": [ 1, 109, 155, 77, 163, 179, 32, 42, 206, 124, 205, 197, 39, 223, 179, 194, 119, 45, 149, 182, 96, 216, 82, 172, 70, 10, 173, 148, 102, 132, 58, 233, 229, 2, 17, 0, 0, 2, 185, 3, 211, 109, 17, 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