Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 65e3039b55fb20378f86fd9e210969a7f51ad213c516a4682b446ab2c9e67df8

Tx prefix hash: 24ffc904ed64e6dbc3c8c3ffc15f495238a5286c6185de72891484e34c31a5d8
Tx public key: 0b17d4f30f84b166d6f1be6c7d7ffe2fb6f4af0462321400eb6b3586ecd3b7ef
Timestamp: 1726177716 Timestamp [UCT]: 2024-09-12 21:48:36 Age [y:d:h:m:s]: 00:249:19:45:53
Block: 1108777 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178407 RingCT/type: yes/0
Extra: 010b17d4f30f84b166d6f1be6c7d7ffe2fb6f4af0462321400eb6b3586ecd3b7ef02110000000de914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b6ec40715c5f24b0e0c26c67799d1b946a1d4a06576f96b878fdd0359c975eea 0.600000000000 1586790 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": 1108787, "vin": [ { "gen": { "height": 1108777 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b6ec40715c5f24b0e0c26c67799d1b946a1d4a06576f96b878fdd0359c975eea" } } ], "extra": [ 1, 11, 23, 212, 243, 15, 132, 177, 102, 214, 241, 190, 108, 125, 127, 254, 47, 182, 244, 175, 4, 98, 50, 20, 0, 235, 107, 53, 134, 236, 211, 183, 239, 2, 17, 0, 0, 0, 13, 233, 20, 221, 21, 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