Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e68ecf9c656e846423a23ed82dd772d7ff925d0433a1460dca4bb8f76eaed892

Tx prefix hash: 4ef933e4a8a03ec9107388d32584c8a5ee15436f8e1b31b60f55289df6a09540
Tx public key: f666a7a8fb4673cb74224ad0727da4669e4884b802e1a7b0e71ec551e3d07333
Timestamp: 1712894477 Timestamp [UCT]: 2024-04-12 04:01:17 Age [y:d:h:m:s]: 00:319:02:40:31
Block: 998626 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 228127 RingCT/type: yes/0
Extra: 01f666a7a8fb4673cb74224ad0727da4669e4884b802e1a7b0e71ec551e3d073330211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e5fcdd35804e7c4902ac4451dc1ab930b30f1fb4fe90de243fe25d425bf86d5 0.600000000000 1459078 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": 998636, "vin": [ { "gen": { "height": 998626 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e5fcdd35804e7c4902ac4451dc1ab930b30f1fb4fe90de243fe25d425bf86d5" } } ], "extra": [ 1, 246, 102, 167, 168, 251, 70, 115, 203, 116, 34, 74, 208, 114, 125, 164, 102, 158, 72, 132, 184, 2, 225, 167, 176, 231, 30, 197, 81, 227, 208, 115, 51, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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