Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da4ab09f1f663d21afaded9b7cda8ffa86aed09bb5d15169cd231665c5e9920f

Tx prefix hash: c204290316dc9dd9cf888a826db1bb343a4410cb7d86af22bcc6a826bb811166
Tx public key: e6ca11f830d5aa38483a5c7c278e680dd3ce1d7e242a63b79d51ffc641d2fdd1
Timestamp: 1733136689 Timestamp [UCT]: 2024-12-02 10:51:29 Age [y:d:h:m:s]: 00:120:00:40:21
Block: 1166367 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 85574 RingCT/type: yes/0
Extra: 01e6ca11f830d5aa38483a5c7c278e680dd3ce1d7e242a63b79d51ffc641d2fdd10211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5125a88fae166225121ac460d403a2e6bf4b2cea092451f6bb408397cbe9ee4f 0.600000000000 1652054 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": 1166377, "vin": [ { "gen": { "height": 1166367 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5125a88fae166225121ac460d403a2e6bf4b2cea092451f6bb408397cbe9ee4f" } } ], "extra": [ 1, 230, 202, 17, 248, 48, 213, 170, 56, 72, 58, 92, 124, 39, 142, 104, 13, 211, 206, 29, 126, 36, 42, 99, 183, 157, 81, 255, 198, 65, 210, 253, 209, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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