Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dfac6fcf70e6a3c93cd262eb34e0eebb6c4f45a9891c9d8ac9e6c5eae09eecb2

Tx prefix hash: 305c4544efab1557e9b536940e30561871d22a5f24bd06ed04c9d7476206fd3e
Tx public key: 961e7b2e92b28784617eb14c72f99503548c57885c4cb6656f53468c335945ac
Timestamp: 1706836295 Timestamp [UCT]: 2024-02-02 01:11:35 Age [y:d:h:m:s]: 01:026:12:49:10
Block: 948412 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 279998 RingCT/type: yes/0
Extra: 01961e7b2e92b28784617eb14c72f99503548c57885c4cb6656f53468c335945ac02110000000210a1748f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3a6f975f1adc11011306dd955e4a9b40515a51d2a2723d3cb53a30c27ed9f341 0.600000000000 1406814 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": 948422, "vin": [ { "gen": { "height": 948412 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3a6f975f1adc11011306dd955e4a9b40515a51d2a2723d3cb53a30c27ed9f341" } } ], "extra": [ 1, 150, 30, 123, 46, 146, 178, 135, 132, 97, 126, 177, 76, 114, 249, 149, 3, 84, 140, 87, 136, 92, 76, 182, 101, 111, 83, 70, 140, 51, 89, 69, 172, 2, 17, 0, 0, 0, 2, 16, 161, 116, 143, 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