← previous blocknext block →recent activity
Analyzing
Block #83,353,615
11 transactions · 7 stateful · 2026-06-24 09:01:18 UTC
Parallelism
82/100
Blocked
29%
Avg conflicts / tx
0.27
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,353,615 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w06w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x95cb8e34…5eba
0x34b655…2a6f
4 touches
1 conflict
0x8b305a3b…1c35
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x18cbab19…7a73
0x34b655…2a6f
2 touches
0 conflicts
0x1c2deff0…6326
0x34b655…2a6f
2 touches
0 conflicts
0x2f2ef5c9…557d
0x34b655…2a6f
2 touches
0 conflicts
0x5d2b5661…df66
0x34b655…2a6f
2 touches
0 conflicts
0x7c19d1af…9ef8
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 0x95cb8e3446…775eba
Audit this contract →
← previous block·next block →recent activity