Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bfd21ef80799db96eb7d31e7d3f3c5dbf93c6d407873966c44896ee2963b4cca

Tx prefix hash: 0f7a773b07233fef3b0c51e61c85b5959966d93528902fd35284c92c60a3726e
Tx public key: 4004def045043814d3fcbd9097e88814c05671213cf0d3299d30cc41f75f6f1c
Timestamp: 1749726473 Timestamp [UCT]: 2025-06-12 11:07:53 Age [y:d:h:m:s]: 00:154:01:18:11
Block: 1303404 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107823 RingCT/type: yes/0
Extra: 014004def045043814d3fcbd9097e88814c05671213cf0d3299d30cc41f75f6f1c021100000004bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 763d1b4e74961c5e0bab2ac1cec6d7c5918ee2b7efcdaecf4dda70b495c6a2c7 0.600000000000 1790985 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": 1303414, "vin": [ { "gen": { "height": 1303404 } } ], "vout": [ { "amount": 600000000, "target": { "key": "763d1b4e74961c5e0bab2ac1cec6d7c5918ee2b7efcdaecf4dda70b495c6a2c7" } } ], "extra": [ 1, 64, 4, 222, 240, 69, 4, 56, 20, 211, 252, 189, 144, 151, 232, 136, 20, 192, 86, 113, 33, 60, 240, 211, 41, 157, 48, 204, 65, 247, 95, 111, 28, 2, 17, 0, 0, 0, 4, 191, 81, 178, 162, 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