← previous blocknext block →recent activity
Analyzing
Block #83,483,460
23 transactions · 20 stateful · 2026-06-24 23:28:37 UTC
Parallelism
74/100
Blocked
35%
Avg conflicts / tx
0.96
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,483,460 · 23 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w07w111w012w113w214w315w416w021w422w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
10 touches
10 conflicts
0x889a1747…a7ce
0x34b655…2a6f
8 touches
6 conflicts
0x68c6b2fa…098d
0x34b655…2a6f
8 touches
6 conflicts
0x13c5b486…d41e
0x34b655…2a6f
4 touches
1 conflict
0x406c6a28…f6e7
0x34b655…2a6f
4 touches
1 conflict
0x680fdd59…e84d
0x34b655…2a6f
4 touches
1 conflict
0x6f1a10f8…5a04
0x34b655…2a6f
4 touches
1 conflict
0x74267bcf…e7b9
0x34b655…2a6f
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: Perpl
10 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity