← previous blocknext block →recent activity
Analyzing
Block #107,817,218
16 transactions · 16 stateful · 2026-09-25 06:06:53 UTC
Parallelism
44/100
Blocked
56%
Avg conflicts / tx
2.31
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #107,817,218 · 16 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w26w37w48w59w610w711w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5cf4d55d…c588
0x34b655…2a6f
18 touches
36 conflicts
0x0fdeef7b…aeb1
0x34b655…2a6f
18 touches
36 conflicts
0x939cdd56…00c8
0x34b655…2a6f
16 touches
28 conflicts
0xa5811d93…8c73
0x34b655…2a6f
16 touches
28 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x973b84cc…0613
0x34b655…2a6f
8 touches
6 conflicts
0x0df117a1…5fc4
0x34b655…2a6f
8 touches
6 conflicts
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
36 conflicts on slot 0x5cf4d55d39…13c588
Audit this contract →
← previous block·next block →recent activity