Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf18538671e908cb61207f9a6c692c89bc02045579f94c096c5edb7723eef812

Tx prefix hash: 203c16c91b08f552d4ca4f839adffdc5b93f3c08456acb835997684de8ebf5ec
Tx public key: 95d1feef051d0c370b9613b12fb89a25bcc1c1cd59a6c43babcba16721c48669
Timestamp: 1743598861 Timestamp [UCT]: 2025-04-02 13:01:01 Age [y:d:h:m:s]: 00:035:03:04:09
Block: 1252717 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 25122 RingCT/type: yes/0
Extra: 0195d1feef051d0c370b9613b12fb89a25bcc1c1cd59a6c43babcba16721c48669021100000002a2ed016b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3e9a304b97efa364ea83f95371f501f4e53ec6fbb4f48a965f857aeaf9e3a3e3 0.600000000000 1739798 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": 1252727, "vin": [ { "gen": { "height": 1252717 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3e9a304b97efa364ea83f95371f501f4e53ec6fbb4f48a965f857aeaf9e3a3e3" } } ], "extra": [ 1, 149, 209, 254, 239, 5, 29, 12, 55, 11, 150, 19, 177, 47, 184, 154, 37, 188, 193, 193, 205, 89, 166, 196, 59, 171, 203, 161, 103, 33, 196, 134, 105, 2, 17, 0, 0, 0, 2, 162, 237, 1, 107, 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