Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a22c9e8151a668349e143fcb0a197f3f1634a96a65b87d96ea7b24416170307

Tx prefix hash: 4080121ae96c648ebbd91bc4cb75d6f7a5be7dba11819d5006ef28cf5e11d3f9
Tx public key: af31520c6fba8f875e3c59570f27402b88dd523105751a167029192f6a5808f8
Timestamp: 1580571203 Timestamp [UCT]: 2020-02-01 15:33:23 Age [y:d:h:m:s]: 04:298:03:26:13
Block: 56722 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1104154 RingCT/type: yes/0
Extra: 01af31520c6fba8f875e3c59570f27402b88dd523105751a167029192f6a5808f8021100000001ff58ae94000000000000000000

1 output(s) for total of 398.159691017000 dcy

stealth address amount amount idx
00: 825da38853d04b178b609da9cf1f4127ca010e8d20c754a78a29883c1f58a7ec 398.159691017000 104529 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": 56732, "vin": [ { "gen": { "height": 56722 } } ], "vout": [ { "amount": 398159691017, "target": { "key": "825da38853d04b178b609da9cf1f4127ca010e8d20c754a78a29883c1f58a7ec" } } ], "extra": [ 1, 175, 49, 82, 12, 111, 186, 143, 135, 94, 60, 89, 87, 15, 39, 64, 43, 136, 221, 82, 49, 5, 117, 26, 22, 112, 41, 25, 47, 106, 88, 8, 248, 2, 17, 0, 0, 0, 1, 255, 88, 174, 148, 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