Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ba58da2e0a5f13a881c586917e8203b9f9e141c62fb672e0ec15ce7b90a92c7

Tx prefix hash: 5335e0bf9af018fe83786869d29cc02739c7df81eb38fea4b40fcbd7ab2f6b23
Tx public key: 9bdcb687d58346c17e0e85db22c11c28f0a50213e67fb3ba050f1b826c02cf99
Timestamp: 1578659845 Timestamp [UCT]: 2020-01-10 12:37:25 Age [y:d:h:m:s]: 05:296:08:07:44
Block: 42663 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1359511 RingCT/type: yes/0
Extra: 019bdcb687d58346c17e0e85db22c11c28f0a50213e67fb3ba050f1b826c02cf99021100000003d81c26c0000000000000000000

1 output(s) for total of 443.241702640000 dcy

stealth address amount amount idx
00: 1fc175306afc0d79d2afde74cd1d5cc14f2fb1e7c99c7c9bdb9e10b2ec84433a 443.241702640000 76940 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": 42673, "vin": [ { "gen": { "height": 42663 } } ], "vout": [ { "amount": 443241702640, "target": { "key": "1fc175306afc0d79d2afde74cd1d5cc14f2fb1e7c99c7c9bdb9e10b2ec84433a" } } ], "extra": [ 1, 155, 220, 182, 135, 213, 131, 70, 193, 126, 14, 133, 219, 34, 193, 28, 40, 240, 165, 2, 19, 230, 127, 179, 186, 5, 15, 27, 130, 108, 2, 207, 153, 2, 17, 0, 0, 0, 3, 216, 28, 38, 192, 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