Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7233b34d83427de9e9cd3eb1c21f275fba5b109f64af7451ef7dcd5c9a21edf

Tx prefix hash: 765b602f9090ec81d83a0a6bf397aae0669ba6c24eb8e06e2cf26e5373972401
Tx public key: b81f3b526c28b010c01c11808d769ce5a2c9ca9550956e0bc787a0a177c03246
Timestamp: 1712741780 Timestamp [UCT]: 2024-04-10 09:36:20 Age [y:d:h:m:s]: 00:343:00:27:50
Block: 997360 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 245275 RingCT/type: yes/0
Extra: 01b81f3b526c28b010c01c11808d769ce5a2c9ca9550956e0bc787a0a177c0324602110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b447ed5916f0d9dd162b784f76475401d14dfa1c2ba670103eb7accc3e624cc6 0.600000000000 1457790 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": 997370, "vin": [ { "gen": { "height": 997360 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b447ed5916f0d9dd162b784f76475401d14dfa1c2ba670103eb7accc3e624cc6" } } ], "extra": [ 1, 184, 31, 59, 82, 108, 40, 176, 16, 192, 28, 17, 128, 141, 118, 156, 229, 162, 201, 202, 149, 80, 149, 110, 11, 199, 135, 160, 161, 119, 192, 50, 70, 2, 17, 0, 0, 0, 4, 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