← previous blocknext block →recent activity
Analyzing
Block #108,654,146
14 transactions · 14 stateful · 2026-09-28 04:19:33 UTC
Parallelism
64/100
Blocked
36%
Avg conflicts / tx
0.57
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,654,146 · 14 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w29w210w311w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3d93ad2c…e747
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x34a6145f…b17d
0x34b655…2a6f
4 touches
1 conflict
0xafb7138a…23ce
0x34b655…2a6f
4 touches
1 conflict
0xbefdde57…cd0e
0x34b655…2a6f
4 touches
1 conflict
0xe9ecfc90…8891
0x34b655…2a6f
4 touches
1 conflict
0x48203298…65cb
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
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 0x3d93ad2c39…a6e747
Audit this contract →
← previous block·next block →recent activity