Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc6e18d3c2cfcca7474649f69ae3e6128595ac1707be57d3e32242795721f2aa

Tx prefix hash: 8fb836724672bc6eb6315e62feb0faa43cd5fa9e8b9333724708a63bf3c82e84
Tx public key: 51cfc42b7a707ba86871a3e1a237f35c3bdd3ceefb191fe15553e56f03954f7e
Timestamp: 1674815206 Timestamp [UCT]: 2023-01-27 10:26:46 Age [y:d:h:m:s]: 02:080:19:14:36
Block: 683829 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 579384 RingCT/type: yes/0
Extra: 0151cfc42b7a707ba86871a3e1a237f35c3bdd3ceefb191fe15553e56f03954f7e0211000000035029cbac000000000000000000

1 output(s) for total of 3.328795721000 dcy

stealth address amount amount idx
00: 8357ec4c2f16eaed0dfd557da74794c500a6374711c6d67c60c3fd84a15e376b 3.328795721000 1126028 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": 683839, "vin": [ { "gen": { "height": 683829 } } ], "vout": [ { "amount": 3328795721, "target": { "key": "8357ec4c2f16eaed0dfd557da74794c500a6374711c6d67c60c3fd84a15e376b" } } ], "extra": [ 1, 81, 207, 196, 43, 122, 112, 123, 168, 104, 113, 163, 225, 162, 55, 243, 92, 59, 221, 60, 238, 251, 25, 31, 225, 85, 83, 229, 111, 3, 149, 79, 126, 2, 17, 0, 0, 0, 3, 80, 41, 203, 172, 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