Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 778dab092f183ee16751c80e1b4666e9d3abcc6d682f8a80956b62c500af1275

Tx prefix hash: 1a04b42e0efd3a0c5c4c3aa349ac8a81034fe9af7fdc9b9c5e4c869e783cd0b2
Tx public key: 0d1d091a84154be5893341faee1404b03da59f2711d8f6cca3e5859937db8232
Timestamp: 1581087114 Timestamp [UCT]: 2020-02-07 14:51:54 Age [y:d:h:m:s]: 05:271:16:54:55
Block: 60395 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1344251 RingCT/type: yes/0
Extra: 010d1d091a84154be5893341faee1404b03da59f2711d8f6cca3e5859937db82320211000000037adf42d3000000000000000000

1 output(s) for total of 387.156996126000 dcy

stealth address amount amount idx
00: e1fb4c2edb2e17cd98ad2debb8a40c24510dc1f710c08b5dca53bfbe7d8cd427 387.156996126000 111322 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": 60405, "vin": [ { "gen": { "height": 60395 } } ], "vout": [ { "amount": 387156996126, "target": { "key": "e1fb4c2edb2e17cd98ad2debb8a40c24510dc1f710c08b5dca53bfbe7d8cd427" } } ], "extra": [ 1, 13, 29, 9, 26, 132, 21, 75, 229, 137, 51, 65, 250, 238, 20, 4, 176, 61, 165, 159, 39, 17, 216, 246, 204, 163, 229, 133, 153, 55, 219, 130, 50, 2, 17, 0, 0, 0, 3, 122, 223, 66, 211, 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