Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb2a34f4c54dbbbfb8e556851c361179d71cd96b6a2f7ce63fc9557d2a96ab0c

Tx prefix hash: 270698f2b767ba5a170469011fed8fd64405d3302fa5c6dca929803b0785f9f9
Tx public key: a0ccff5703f1fb8b6eddfd40f81edd472b2439feeda9400e47f9d5f1ee365d2a
Timestamp: 1703878549 Timestamp [UCT]: 2023-12-29 19:35:49 Age [y:d:h:m:s]: 01:106:18:37:01
Block: 923899 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 337431 RingCT/type: yes/0
Extra: 01a0ccff5703f1fb8b6eddfd40f81edd472b2439feeda9400e47f9d5f1ee365d2a0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 136a143820c3a71b289d3aff197c69cc0bcb966e9c78ba32c59da68f7bdf60be 0.600000000000 1381637 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": 923909, "vin": [ { "gen": { "height": 923899 } } ], "vout": [ { "amount": 600000000, "target": { "key": "136a143820c3a71b289d3aff197c69cc0bcb966e9c78ba32c59da68f7bdf60be" } } ], "extra": [ 1, 160, 204, 255, 87, 3, 241, 251, 139, 110, 221, 253, 64, 248, 30, 221, 71, 43, 36, 57, 254, 237, 169, 64, 14, 71, 249, 213, 241, 238, 54, 93, 42, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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