← previous blocknext block →recent activity
Analyzing
Block #108,499,096
24 transactions · 22 stateful · 2026-09-27 15:18:45 UTC
Parallelism
79/100
Blocked
36%
Avg conflicts / tx
0.75
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,499,096 · 24 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
2w05w16w210w011w213w114w015w116w220w022w323w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5e2ea201…12de
0x34b655…2a6f
6 touches
3 conflicts
0x646cebfb…2a78
0x34b655…2a6f
6 touches
3 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
6 touches
3 conflicts
0x4c29ecd5…58b6
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
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 0x5e2ea201dc…2012de
Audit this contract →
← previous block·next block →recent activity