← previous blocknext block →recent activity
Analyzing
Block #107,838,866
34 transactions · 28 stateful · 2026-09-25 07:55:50 UTC
Parallelism
82/100
Blocked
25%
Avg conflicts / tx
0.38
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #107,838,866 · 34 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
1w02w114w015w116w217w318w419w524w025w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x25144f94…1854
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x9ad325f5…cc43
0x34b655…2a6f
6 touches
3 conflicts
0xa05832d1…d787
0x34b655…2a6f
6 touches
3 conflicts
0x3750b746…5a9e
0x34b655…2a6f
6 touches
3 conflicts
0xba5743c7…21c6
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x31d88d27…7617
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 0x25144f94f3…701854
Audit this contract →
← previous block·next block →recent activity