← previous blocknext block →recent activity
Analyzing
Block #107,823,860
20 transactions · 18 stateful · 2026-09-25 06:40:19 UTC
Parallelism
80/100
Blocked
33%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #107,823,860 · 20 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
1w02w13w24w07w111w012w113w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x25144f94…1854
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x6d43ee99…bdda
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0xd8ee0b47…f7be
0xd32edf…ff58
5 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x125f12…a50b
4 touches
1 conflict
0x00000000…0009
0x125f12…a50b
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