Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5435f76a9fde4ffd8acc552e8f63bfd136a40727a328e6d171c71be603a9319a

Tx prefix hash: 564aef4cab07071f7ea7907c7a1c1c16d2a6a8a63c2402902e0f24b0ba248654
Tx public key: 12567ed08e8f97493e7dea403179d7a63ce5035366a9daa2d9b52ca1e1d116e3
Timestamp: 1628660291 Timestamp [UCT]: 2021-08-11 05:38:11 Age [y:d:h:m:s]: 03:275:04:07:44
Block: 311577 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 969646 RingCT/type: yes/0
Extra: 0112567ed08e8f97493e7dea403179d7a63ce5035366a9daa2d9b52ca1e1d116e302110000000e17696b73000000000000000000

1 output(s) for total of 56.966105622000 dcy

stealth address amount amount idx
00: 6d7890e684e7f1d51159784057779200b8b2405b8d88d1f2f86171cebe48f3a4 56.966105622000 648438 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": 311587, "vin": [ { "gen": { "height": 311577 } } ], "vout": [ { "amount": 56966105622, "target": { "key": "6d7890e684e7f1d51159784057779200b8b2405b8d88d1f2f86171cebe48f3a4" } } ], "extra": [ 1, 18, 86, 126, 208, 142, 143, 151, 73, 62, 125, 234, 64, 49, 121, 215, 166, 60, 229, 3, 83, 102, 169, 218, 162, 217, 181, 44, 161, 225, 209, 22, 227, 2, 17, 0, 0, 0, 14, 23, 105, 107, 115, 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