Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60ad0cceafbd33e11887c2670f3f6a14fe27be0c521c162436e70c86c2eb5435

Tx prefix hash: c3deb5d1c5fefad5234bedc9f0f0436571d3e3d23a4191b2d25e662245354a18
Tx public key: 92acb4934106cc409d5d71dbdc4c4199872366e83d0fb7432d876105a00ee26c
Timestamp: 1709779606 Timestamp [UCT]: 2024-03-07 02:46:46 Age [y:d:h:m:s]: 01:252:06:47:38
Block: 972834 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 439027 RingCT/type: yes/0
Extra: 0192acb4934106cc409d5d71dbdc4c4199872366e83d0fb7432d876105a00ee26c02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8860ea05f8509e14ecea3b4c723419c909b616b6b0eb2b82de4d56be3fec5a5a 0.600000000000 1432753 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": 972844, "vin": [ { "gen": { "height": 972834 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8860ea05f8509e14ecea3b4c723419c909b616b6b0eb2b82de4d56be3fec5a5a" } } ], "extra": [ 1, 146, 172, 180, 147, 65, 6, 204, 64, 157, 93, 113, 219, 220, 76, 65, 153, 135, 35, 102, 232, 61, 15, 183, 67, 45, 135, 97, 5, 160, 14, 226, 108, 2, 17, 0, 0, 0, 3, 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