Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 341a828dea0ca5152faf9ee3b74bb5a78e3ca45ffe44cfa98576adf3c49e9617

Tx prefix hash: e81671fc48c9e46df839e21ddeacb94eba1dad5cabd7cbbb2d3c729ad4cf7773
Tx public key: f40028a31ca4e606f85c414d197ce2d099efbf9ddaf7d03edb6b744bea5c0260
Timestamp: 1722327421 Timestamp [UCT]: 2024-07-30 08:17:01 Age [y:d:h:m:s]: 00:235:19:45:40
Block: 1076846 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 168443 RingCT/type: yes/0
Extra: 01f40028a31ca4e606f85c414d197ce2d099efbf9ddaf7d03edb6b744bea5c02600211000000018c7e50ca000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d45581f918c53456bfa716881e347f4c561d9934c7b47c36baf7feff852aa24 0.600000000000 1549387 of 15

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": 1076856, "vin": [ { "gen": { "height": 1076846 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d45581f918c53456bfa716881e347f4c561d9934c7b47c36baf7feff852aa24" } } ], "extra": [ 1, 244, 0, 40, 163, 28, 164, 230, 6, 248, 92, 65, 77, 25, 124, 226, 208, 153, 239, 191, 157, 218, 247, 208, 62, 219, 107, 116, 75, 234, 92, 2, 96, 2, 17, 0, 0, 0, 1, 140, 126, 80, 202, 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