← previous blocknext block →recent activity
Analyzing
Block #108,960,165
21 transactions · 18 stateful · 2026-09-29 06:03:59 UTC
Parallelism
81/100
Blocked
33%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #108,960,165 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w114w015w116w217w318w219w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe8a7222d…9ca2
0x34b655…2a6f
8 touches
6 conflicts
0x941bd594…21fd
0x34b655…2a6f
8 touches
6 conflicts
0xc53799eb…d928
0x34b655…2a6f
6 touches
3 conflicts
0xa9af9157…5a6e
0x34b655…2a6f
6 touches
3 conflicts
0xc4c059d8…185d
0x34b655…2a6f
6 touches
3 conflicts
0x4b36c7dd…da26
0x34b655…2a6f
4 touches
1 conflict
0xbefdde57…cd0e
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
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
6 conflicts on slot 0xe8a7222d42…539ca2
Audit this contract →
← previous block·next block →recent activity