← previous blocknext block →recent activity
Analyzing
Block #83,639,234
25 transactions · 22 stateful · 2026-06-25 16:48:03 UTC
Parallelism
88/100
Blocked
18%
Avg conflicts / tx
0.24
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,639,234 · 25 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
4w06w17w08w110w216w022w023w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x37a276a3…673f
0x34b655…2a6f
6 touches
3 conflicts
0x0213af2e…926e
0x34b655…2a6f
4 touches
1 conflict
0x035b1f21…8a70
0x34b655…2a6f
4 touches
1 conflict
0x0782e1b1…f10a
0x34b655…2a6f
4 touches
1 conflict
0x0faf7d44…c1cb
0x34b655…2a6f
4 touches
1 conflict
0x30c5329c…711c
0x34b655…2a6f
4 touches
1 conflict
0x4f4bdabd…ffba
0x34b655…2a6f
4 touches
1 conflict
0x71391185…0caa
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
3 conflicts on slot 0x37a276a33f…0f673f
Audit this contract →
← previous block·next block →recent activity