← previous blocknext block →recent activity
Analyzing
Block #107,841,389
24 transactions · 20 stateful · 2026-09-25 08:08:32 UTC
Parallelism
67/100
Blocked
40%
Avg conflicts / tx
0.75
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #107,841,389 · 24 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w26w311w414w015w516w617w722w023w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x4e96add8…59cd
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xa0a8c7a5…3422
0x34b655…2a6f
6 touches
3 conflicts
0x9ac6e2c9…e02e
0x34b655…2a6f
6 touches
3 conflicts
0x3a663e9a…a9ce
0x508254…98bd
4 touches
1 conflict
0x00f245ce…1e10
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
6 conflicts on slot 0x49890ced8d…316f23
Audit this contract →
← previous block·next block →recent activity