Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e7f247d682f9294771e91e47fd3fcd2dd19559bc67bf41a27bbddb22f39bdd83

Tx prefix hash: 363d5951f8c72dd85c83d9101814e8857924dc28c1cd73975335ff94c797b167
Tx public key: e62ba5a9a1e835a34641c5c2071d00f3ea09a69ab58c08d9fe48ce7cc2c7ffb0
Timestamp: 1714150245 Timestamp [UCT]: 2024-04-26 16:50:45 Age [y:d:h:m:s]: 00:257:19:27:38
Block: 1009057 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184534 RingCT/type: yes/0
Extra: 01e62ba5a9a1e835a34641c5c2071d00f3ea09a69ab58c08d9fe48ce7cc2c7ffb00211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.607780000000 dcy

stealth address amount amount idx
00: 3a8c422593923329cef97ef9b8363a588cdcc648572155b69057f62dd9c80621 0.607780000000 1470613 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": 1009067, "vin": [ { "gen": { "height": 1009057 } } ], "vout": [ { "amount": 607780000, "target": { "key": "3a8c422593923329cef97ef9b8363a588cdcc648572155b69057f62dd9c80621" } } ], "extra": [ 1, 230, 43, 165, 169, 161, 232, 53, 163, 70, 65, 197, 194, 7, 29, 0, 243, 234, 9, 166, 154, 181, 140, 8, 217, 254, 72, 206, 124, 194, 199, 255, 176, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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