← previous blocknext block →recent activity
Analyzing
Block #83,632,052
20 transactions · 18 stateful · 2026-06-25 16:00:03 UTC
Parallelism
80/100
Blocked
33%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,632,052 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w29w311w012w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…00fc
0xd45826…f134
6 touches
3 conflicts
0x8ebf69ec…edd2
0xd45826…f134
6 touches
3 conflicts
0x00000000…0161
0xd45826…f134
6 touches
3 conflicts
0x8ebf69ec…edcd
0xd45826…f134
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001b
0x1b6862…e19c
4 touches
1 conflict
0xba5743c7…21c2
0x1b6862…e19c
4 touches
1 conflict
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: 0xd458261e…e6f134
3 conflicts on slot 0x0000000000…0000fc
Audit this contract →
← previous block·next block →recent activity