← previous blocknext block →recent activity
Analyzing
Block #107,822,962
24 transactions · 24 stateful · 2026-09-25 06:35:47 UTC
Parallelism
83/100
Blocked
33%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #107,822,962 · 24 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
2w03w18w09w111w012w013w114w215w216w317w122w023w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdaf11f45…b255
0x34b655…2a6f
6 touches
3 conflicts
0xabce9cc8…3c73
0x34b655…2a6f
6 touches
3 conflicts
0x64275949…d698
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x6d955786…1327
0x34b655…2a6f
6 touches
3 conflicts
0x6a256e72…a80a
0x34b655…2a6f
4 touches
1 conflict
0xe2995197…337c
0xcc9410…4c10
4 touches
1 conflict
0x0e9209dc…2fe1
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 0xdaf11f45f1…bbb255
Audit this contract →
← previous block·next block →recent activity