← previous blocknext block →recent activity
Analyzing
Block #107,802,738
21 transactions · 20 stateful · 2026-09-25 04:54:01 UTC
Parallelism
76/100
Blocked
55%
Avg conflicts / tx
1.05
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #107,802,738 · 21 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
1w02w14w06w17w28w29w010w111w212w313w414w115w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0x3cb7ee74…b8a5
0x34b655…2a6f
8 touches
6 conflicts
0x5900e8aa…2391
0x34b655…2a6f
8 touches
6 conflicts
0x588380ee…0a5c
0x34b655…2a6f
8 touches
6 conflicts
0x6aeef401…c7f2
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x9e22394b…a9ba
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
10 conflicts on slot 0x49890ced8d…316f23
Audit this contract →
← previous block·next block →recent activity