← previous blocknext block →recent activity
Analyzing
Block #107,278,417
29 transactions · 27 stateful · 2026-09-23 08:52:51 UTC
Parallelism
76/100
Blocked
52%
Avg conflicts / tx
1.34
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #107,278,417 · 29 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
1w02w13w24w15w36w47w523w324w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf1bbd371…e541
0x34b655…2a6f
12 touches
15 conflicts
0xcb05abdb…baac
0x34b655…2a6f
12 touches
15 conflicts
0x42522e76…2592
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x1d6cb721…c88c
0x34b655…2a6f
8 touches
6 conflicts
0x3b457555…f5ff
0x34b655…2a6f
8 touches
6 conflicts
0x9531fd7d…6c4d
0x34b655…2a6f
8 touches
6 conflicts
0xbd9491f7…dd92
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
15 conflicts on slot 0xf1bbd371ee…44e541
Audit this contract →
← previous block·next block →recent activity