Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3edf3753824aa692e2ffbf1e1ba6555fbe44342a781f97509ec303c9e3a734cd

Tx prefix hash: aa4f9dc276e334d81c301dddfa4beec063a817d631588fb60c34ca20acf1f187
Tx public key: 8a9bffdbe4b6ed6a9b1ffb68dbe98b4da1a4ba3f5dff04a54795d26b88bf1ca4
Timestamp: 1734150402 Timestamp [UCT]: 2024-12-14 04:26:42 Age [y:d:h:m:s]: 00:117:18:23:11
Block: 1174769 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83950 RingCT/type: yes/0
Extra: 018a9bffdbe4b6ed6a9b1ffb68dbe98b4da1a4ba3f5dff04a54795d26b88bf1ca4021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cfc700ff37743e3f65f46576b7b10ceaedff9bbd5daf8e6007b15b03e7f604de 0.600000000000 1660964 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": 1174779, "vin": [ { "gen": { "height": 1174769 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cfc700ff37743e3f65f46576b7b10ceaedff9bbd5daf8e6007b15b03e7f604de" } } ], "extra": [ 1, 138, 155, 255, 219, 228, 182, 237, 106, 155, 31, 251, 104, 219, 233, 139, 77, 161, 164, 186, 63, 93, 255, 4, 165, 71, 149, 210, 107, 136, 191, 28, 164, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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