Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a8ea7facceddcc74f614f83d907613b4bba1e119bac5c5b403e472fdd267f53

Tx prefix hash: 39b5541bc1a754780b33ed08e93b80621b413705b65468bbfc62816bf9ab52ac
Tx public key: 4b9f5b2e4f898bbe27c18891932e91aa897ecfe9f0f24f1f07a854f3694bd8ac
Timestamp: 1723372037 Timestamp [UCT]: 2024-08-11 10:27:17 Age [y:d:h:m:s]: 00:310:15:59:18
Block: 1085512 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 221844 RingCT/type: yes/0
Extra: 014b9f5b2e4f898bbe27c18891932e91aa897ecfe9f0f24f1f07a854f3694bd8ac021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f80e8191fdaefb9cc0ac7c3e622fc5293993b268ef529e2c823a7682d288b052 0.600000000000 1560099 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": 1085522, "vin": [ { "gen": { "height": 1085512 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f80e8191fdaefb9cc0ac7c3e622fc5293993b268ef529e2c823a7682d288b052" } } ], "extra": [ 1, 75, 159, 91, 46, 79, 137, 139, 190, 39, 193, 136, 145, 147, 46, 145, 170, 137, 126, 207, 233, 240, 242, 79, 31, 7, 168, 84, 243, 105, 75, 216, 172, 2, 17, 0, 0, 0, 7, 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