← previous blocknext block →recent activity
Analyzing
Block #107,841,384
21 transactions · 18 stateful · 2026-09-25 08:08:30 UTC
Parallelism
71/100
Blocked
50%
Avg conflicts / tx
0.67
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #107,841,384 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w29w310w411w512w013w017w118w219w120w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3ff9db2e…22f6
0x34b655…2a6f
8 touches
6 conflicts
0x242a9fee…2718
0x34b655…2a6f
6 touches
3 conflicts
0x3a663e9a…a9c5
0x508254…98bd
6 touches
3 conflicts
0x3a663e9a…a9d0
0x508254…98bd
6 touches
3 conflicts
0xdcae6e9b…e335
0xd32edf…ff58
5 touches
3 conflicts
0xd5b10148…e638
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x43e3decb…be40
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 0x3ff9db2e2d…9122f6
Audit this contract →
← previous block·next block →recent activity