← previous blocknext block →recent activity
Analyzing
Block #107,807,072
29 transactions · 25 stateful · 2026-09-25 05:15:49 UTC
Parallelism
86/100
Blocked
32%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #107,807,072 · 29 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w18w010w112w016w018w019w120w021w124w225w026w127w228w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x3a663e9a…a9c5
0x508254…98bd
6 touches
3 conflicts
0x3a663e9a…a9c7
0x508254…98bd
6 touches
3 conflicts
0x3a663e9a…a9ca
0x508254…98bd
6 touches
3 conflicts
0x3a663e9a…a9d3
0x508254…98bd
6 touches
3 conflicts
0x3a663e9a…a9d4
0x508254…98bd
6 touches
3 conflicts
0x134d29ed…644d
0x508254…98bd
4 touches
1 conflict
0x134d29ed…645d
0x508254…98bd
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity