← previous blocknext block →recent activity
Analyzing
Block #107,839,723
50 transactions · 38 stateful · 2026-09-25 08:00:09 UTC
Parallelism
86/100
Blocked
55%
Avg conflicts / tx
0.94
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #107,839,723 · 50 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w210w311w314w015w116w217w326w427w435w536w545w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x422d5490…52d9
0x34b655…2a6f
10 touches
10 conflicts
0xea02471d…1542
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x1b5d2e60…99b5
0x34b655…2a6f
8 touches
6 conflicts
0x2877f440…c2c8
0x34b655…2a6f
8 touches
6 conflicts
0x53b4ef2b…8a05
0x34b655…2a6f
8 touches
6 conflicts
0x545e527e…0eb0
0x34b655…2a6f
8 touches
6 conflicts
0x5f251b96…6054
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
10 conflicts on slot 0x422d549061…1f52d9
Audit this contract →
← previous block·next block →recent activity