← previous blocknext block →recent activity
Analyzing
Block #107,838,826
20 transactions · 19 stateful · 2026-09-25 07:55:38 UTC
Parallelism
75/100
Blocked
32%
Avg conflicts / tx
0.6
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #107,838,826 · 20 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
3w08w09w110w211w312w417w018w119w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa882817c…38c4
0x34b655…2a6f
10 touches
10 conflicts
0x4d205b22…b005
0x34b655…2a6f
10 touches
10 conflicts
0x5e2ea201…12de
0x34b655…2a6f
8 touches
6 conflicts
0x31d88d27…7617
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0xb44232d0…a5f0
0x34b655…2a6f
6 touches
3 conflicts
0x28e2f7c3…e848
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
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 0xa882817cbe…1b38c4
Audit this contract →
← previous block·next block →recent activity