Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea6c58536e834cf7819d8d040bb72f488353a80a69d3966c8cea1f3645078ab4

Tx prefix hash: acebd53060adca5991ba08d9c57775edc7c41c9888cc80cfbc1b27e071e61bef
Tx public key: 8d7b0f24942de5253f69faa9d5281f5fd5e18605d68c31c729dc747db18a0287
Timestamp: 1641067644 Timestamp [UCT]: 2022-01-01 20:07:24 Age [y:d:h:m:s]: 03:023:04:10:16
Block: 408378 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 795540 RingCT/type: yes/0
Extra: 018d7b0f24942de5253f69faa9d5281f5fd5e18605d68c31c729dc747db18a0287021100000004a272b9cb000000000000000000

1 output(s) for total of 27.219146268000 dcy

stealth address amount amount idx
00: db17823e6d52ed8dbd442f8b94d564911c92c15200da1d688bd5a86ea6e42e81 27.219146268000 810395 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": 408388, "vin": [ { "gen": { "height": 408378 } } ], "vout": [ { "amount": 27219146268, "target": { "key": "db17823e6d52ed8dbd442f8b94d564911c92c15200da1d688bd5a86ea6e42e81" } } ], "extra": [ 1, 141, 123, 15, 36, 148, 45, 229, 37, 63, 105, 250, 169, 213, 40, 31, 95, 213, 225, 134, 5, 214, 140, 49, 199, 41, 220, 116, 125, 177, 138, 2, 135, 2, 17, 0, 0, 0, 4, 162, 114, 185, 203, 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