Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cfa7a40719322cdcdd28901b4185acdd0692efa72dd757993cec7c0850d0b8d7

Tx prefix hash: d604a17042f97712755c819a765fbdff6c85f60c54cc8e4fc4be522cc235be12
Tx public key: 7e0c654f1a46fd137eadf263baf89a30861b1ee7efd111b53b31981bc2f93923
Timestamp: 1582977392 Timestamp [UCT]: 2020-02-29 11:56:32 Age [y:d:h:m:s]: 05:073:21:57:56
Block: 74054 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1207174 RingCT/type: yes/0
Extra: 017e0c654f1a46fd137eadf263baf89a30861b1ee7efd111b53b31981bc2f9392302110000036103d36d11000000000000000000

1 output(s) for total of 348.842311363000 dcy

stealth address amount amount idx
00: 15209ab04a52be43046eb04d808765c92ac35ae867327bc7743e88e0160cceb0 348.842311363000 136860 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": 74064, "vin": [ { "gen": { "height": 74054 } } ], "vout": [ { "amount": 348842311363, "target": { "key": "15209ab04a52be43046eb04d808765c92ac35ae867327bc7743e88e0160cceb0" } } ], "extra": [ 1, 126, 12, 101, 79, 26, 70, 253, 19, 126, 173, 242, 99, 186, 248, 154, 48, 134, 27, 30, 231, 239, 209, 17, 181, 59, 49, 152, 27, 194, 249, 57, 35, 2, 17, 0, 0, 3, 97, 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