Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5533474499327946abdbe554ffc4cb3973bb3807153f9c80ddb8c9aae15f6d22

Tx prefix hash: 9d7665c76272b7ea0520415dd8490452a4518318dfa3a85677e7eab07910293a
Tx public key: 64e057e5cf113036e87f8fbca3f55efb32933cfe9ada0c7cd7e36152b4632fc7
Timestamp: 1661473812 Timestamp [UCT]: 2022-08-26 00:30:12 Age [y:d:h:m:s]: 02:281:09:37:57
Block: 573866 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 722402 RingCT/type: yes/0
Extra: 0164e057e5cf113036e87f8fbca3f55efb32933cfe9ada0c7cd7e36152b4632fc702110000001ae6d27f9c000000000000000000

1 output(s) for total of 7.700941356000 dcy

stealth address amount amount idx
00: 10060edbff478ec6116f1a3e104a36e7d4cbed59ce7a620dc66b52f1c57d6bad 7.700941356000 1007164 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": 573876, "vin": [ { "gen": { "height": 573866 } } ], "vout": [ { "amount": 7700941356, "target": { "key": "10060edbff478ec6116f1a3e104a36e7d4cbed59ce7a620dc66b52f1c57d6bad" } } ], "extra": [ 1, 100, 224, 87, 229, 207, 17, 48, 54, 232, 127, 143, 188, 163, 245, 94, 251, 50, 147, 60, 254, 154, 218, 12, 124, 215, 227, 97, 82, 180, 99, 47, 199, 2, 17, 0, 0, 0, 26, 230, 210, 127, 156, 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