← previous blocknext block →recent activity
Analyzing
Block #107,816,919
20 transactions · 19 stateful · 2026-09-25 06:05:22 UTC
Parallelism
70/100
Blocked
37%
Avg conflicts / tx
0.6
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #107,816,919 · 20 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
4w06w19w010w112w213w314w315w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa23b9051…392f
0x34b655…2a6f
8 touches
6 conflicts
0x2328941c…84d3
0x34b655…2a6f
6 touches
3 conflicts
0x6cdba66e…51e2
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x2b856d86…7988
0x34b655…2a6f
6 touches
3 conflicts
0xe98b562e…57e1
0x34b655…2a6f
4 touches
1 conflict
0x0ed7cc0b…ee52
0x34b655…2a6f
4 touches
1 conflict
0x12866eb3…771f
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 0xa23b905120…88392f
Audit this contract →
← previous block·next block →recent activity