← previous blocknext block →recent activity
Analyzing
Block #108,640,891
15 transactions · 13 stateful · 2026-09-28 03:12:49 UTC
Parallelism
60/100
Blocked
54%
Avg conflicts / tx
0.8
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #108,640,891 · 15 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
1w02w13w04w15w28w39w411w012w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xb991f1e1…5e32
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0xed8224d3…528e
0x34b655…2a6f
4 touches
1 conflict
0x970da48a…345b
0x34b655…2a6f
4 touches
1 conflict
0x260e7925…594f
0x34b655…2a6f
4 touches
1 conflict
0x280e43ac…b67a
0x34b655…2a6f
4 touches
1 conflict
0x37f93b32…cc57
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 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity