Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e791b880460fbec89e0c0aaf59290667cab076cfc8ffd3bfb4865f36556075b0

Tx prefix hash: 538abf9abed0b78af87be30c7fc1ec8f6189e4974fb2bd33d3a91d3aa0f7de65
Tx public key: 19b0ef9fc88ef998dca6ec5c385cc12467c6f2b695c71e83aedbb4511804c33a
Timestamp: 1627983943 Timestamp [UCT]: 2021-08-03 09:45:43 Age [y:d:h:m:s]: 03:117:10:00:41
Block: 306434 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 856613 RingCT/type: yes/0
Extra: 0119b0ef9fc88ef998dca6ec5c385cc12467c6f2b695c71e83aedbb4511804c33a02110000001fe6f80b5a000000000000000000

1 output(s) for total of 59.247841461000 dcy

stealth address amount amount idx
00: 5df80c80d9f62e29435a5d35e201be4861dec68cfc69a339f37710e6fdd7d62d 59.247841461000 639007 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": 306444, "vin": [ { "gen": { "height": 306434 } } ], "vout": [ { "amount": 59247841461, "target": { "key": "5df80c80d9f62e29435a5d35e201be4861dec68cfc69a339f37710e6fdd7d62d" } } ], "extra": [ 1, 25, 176, 239, 159, 200, 142, 249, 152, 220, 166, 236, 92, 56, 92, 193, 36, 103, 198, 242, 182, 149, 199, 30, 131, 174, 219, 180, 81, 24, 4, 195, 58, 2, 17, 0, 0, 0, 31, 230, 248, 11, 90, 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