Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f1e93c28afe6590beed9efadedb752b9753f86defbe49c916f6dadc16db580c

Tx prefix hash: b38a4a1bf93978f45eb181c700fa9b0b101b8f0d29aeddb910bc4dae5d13bb4e
Tx public key: f8bd100069664b178ecec70cf2cfe0a2b5ed39abcb57428684a5e38e192b58e6
Timestamp: 1719002491 Timestamp [UCT]: 2024-06-21 20:41:31 Age [y:d:h:m:s]: 00:318:22:52:51
Block: 1049263 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 227963 RingCT/type: yes/0
Extra: 01f8bd100069664b178ecec70cf2cfe0a2b5ed39abcb57428684a5e38e192b58e60211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bbbb419eb80acb61053237246d43cb74038802e30a4a952693a77bfdae7d60c4 0.600000000000 1519362 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": 1049273, "vin": [ { "gen": { "height": 1049263 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bbbb419eb80acb61053237246d43cb74038802e30a4a952693a77bfdae7d60c4" } } ], "extra": [ 1, 248, 189, 16, 0, 105, 102, 75, 23, 142, 206, 199, 12, 242, 207, 224, 162, 181, 237, 57, 171, 203, 87, 66, 134, 132, 165, 227, 142, 25, 43, 88, 230, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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