← previous blocknext block →recent activity
Analyzing
Block #107,823,733
11 transactions · 10 stateful · 2026-09-25 06:39:40 UTC
Parallelism
55/100
Blocked
40%
Avg conflicts / tx
0.64
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #107,823,733 · 11 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
5w06w17w28w39w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0a1eb0a7…653a
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0xe17b6c90…de9f
0x34b655…2a6f
6 touches
3 conflicts
0xcf6237f6…f121
0x34b655…2a6f
6 touches
3 conflicts
0x14fe1598…d0ba
0x34b655…2a6f
4 touches
1 conflict
0x25144f94…1854
0x34b655…2a6f
4 touches
1 conflict
0x301e1c77…9e30
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
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 0x0a1eb0a754…53653a
Audit this contract →
← previous block·next block →recent activity