← previous blocknext block →recent activity
Analyzing
Block #108,664,408
17 transactions · 13 stateful · 2026-09-28 05:11:13 UTC
Parallelism
82/100
Blocked
31%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #108,664,408 · 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
5w08w09w110w111w212w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x85d7a70d…ec29
0x34b655…2a6f
4 touches
1 conflict
0xaa3cf307…30e8
0x34b655…2a6f
4 touches
1 conflict
0xb991f1e1…5e32
0x34b655…2a6f
4 touches
1 conflict
0xcd0e79e1…4c56
0x34b655…2a6f
4 touches
1 conflict
0xf3b3a6e9…8cd2
0x34b655…2a6f
4 touches
1 conflict
0x02ee3e98…d4fc
0x34b655…2a6f
4 touches
1 conflict
0x07890a2a…be99
0x34b655…2a6f
4 touches
1 conflict
0x4073f47e…39e6
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
1 conflict on slot 0x85d7a70d33…a6ec29
Audit this contract →
← previous block·next block →recent activity