Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9bb3410b8857f1ba43c861583758fa84688dbeb2cffa7b90a625e5701db6f8b5

Tx prefix hash: 1b08af17974cae6e0d550d989313ec9b315f3fea5b279a59b72d23ba93a05b06
Tx public key: 65a3e6a3e2be2900e62302d56d61fe90d2948ba4b3733e2bd01454c0c29d8530
Timestamp: 1712460600 Timestamp [UCT]: 2024-04-07 03:30:00 Age [y:d:h:m:s]: 01:216:12:04:44
Block: 995016 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 413432 RingCT/type: yes/0
Extra: 0165a3e6a3e2be2900e62302d56d61fe90d2948ba4b3733e2bd01454c0c29d853002110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: df2462c682530d27a9c2f446862f296dbc70a6219000886604033c946efefa42 0.600000000000 1455420 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": 995026, "vin": [ { "gen": { "height": 995016 } } ], "vout": [ { "amount": 600000000, "target": { "key": "df2462c682530d27a9c2f446862f296dbc70a6219000886604033c946efefa42" } } ], "extra": [ 1, 101, 163, 230, 163, 226, 190, 41, 0, 230, 35, 2, 213, 109, 97, 254, 144, 210, 148, 139, 164, 179, 115, 62, 43, 208, 20, 84, 192, 194, 157, 133, 48, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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