← previous blocknext block →recent activity
Analyzing
Block #83,633,213
17 transactions · 14 stateful · 2026-06-25 16:07:49 UTC
Parallelism
82/100
Blocked
21%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,633,213 · 17 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w07w110w213w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe2e45419…f17b
0x34b655…2a6f
4 touches
1 conflict
0x619f5683…5bd4
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x1adc27b8…cb3a
0x34b655…2a6f
2 touches
0 conflicts
0x1af777a9…b403
0x34b655…2a6f
2 touches
0 conflicts
0x84d5ecbc…da2e
0x34b655…2a6f
2 touches
0 conflicts
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: Perpl
1 conflict on slot 0xe2e454194e…59f17b
Audit this contract →
← previous block·next block →recent activity