← previous blocknext block →recent activity
Analyzing
Block #107,839,377
18 transactions · 16 stateful · 2026-09-25 07:58:24 UTC
Parallelism
72/100
Blocked
38%
Avg conflicts / tx
0.56
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #107,839,377 · 18 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
6w07w18w29w110w312w415w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x6a256e72…a80a
0x34b655…2a6f
6 touches
3 conflicts
0xb195cffa…8098
0x34b655…2a6f
6 touches
3 conflicts
0x1abfd3ae…2999
0x34b655…2a6f
4 touches
1 conflict
0x32947f75…255a
0x34b655…2a6f
4 touches
1 conflict
0x5e26f4ec…9b6c
0x34b655…2a6f
4 touches
1 conflict
0x0ed7cc0b…ee52
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 0x42522e76ce…082592
Audit this contract →
← previous block·next block →recent activity