Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d93a89b9ac9f905ff1ffb223822debc14d4a9e52b348b7432f8aca028c6f7bdb

Tx prefix hash: 882a1e801c0154ce360b655fe056ef7a0759cae82adfae93597192ac378ef267
Tx public key: 9072a2263f50c0f0c16e7f22f288ce7e3154c0c7369471eaf4f45640fa7b6614
Timestamp: 1578787030 Timestamp [UCT]: 2020-01-11 23:57:10 Age [y:d:h:m:s]: 04:267:10:37:29
Block: 43525 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1080676 RingCT/type: yes/0
Extra: 019072a2263f50c0f0c16e7f22f288ce7e3154c0c7369471eaf4f45640fa7b66140211000000372264afe6000000000000000000

1 output(s) for total of 440.343849967000 dcy

stealth address amount amount idx
00: 2cc943dc5e3026bfa4d8229aaf4e32d22933934924e418e7cd82ae82db7c7666 440.343849967000 78871 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": 43535, "vin": [ { "gen": { "height": 43525 } } ], "vout": [ { "amount": 440343849967, "target": { "key": "2cc943dc5e3026bfa4d8229aaf4e32d22933934924e418e7cd82ae82db7c7666" } } ], "extra": [ 1, 144, 114, 162, 38, 63, 80, 192, 240, 193, 110, 127, 34, 242, 136, 206, 126, 49, 84, 192, 199, 54, 148, 113, 234, 244, 244, 86, 64, 250, 123, 102, 20, 2, 17, 0, 0, 0, 55, 34, 100, 175, 230, 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