← previous blocknext block →recent activity
Analyzing
Block #83,632,803
18 transactions · 16 stateful · 2026-06-25 16:05:05 UTC
Parallelism
83/100
Blocked
38%
Avg conflicts / tx
0.39
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,632,803 · 18 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
1w02w13w14w05w16w07w18w214w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x07994b5a…d505
0x34b655…2a6f
6 touches
3 conflicts
0x022f72c3…07b6
0xc8689a…ee79
6 touches
3 conflicts
0x82dd2252…e1ce
0x34b655…2a6f
6 touches
3 conflicts
0x5396d712…a139
0x34b655…2a6f
6 touches
3 conflicts
0x02312272…08aa
0x34b655…2a6f
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0xe334a6b5…173c
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0xaa7ee7…f0e4
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
3 conflicts on slot 0x07994b5aa3…b2d505
Audit this contract →
← previous block·next block →recent activity