← previous blocknext block →recent activity
Analyzing
Block #107,823,144
13 transactions · 13 stateful · 2026-09-25 06:36:42 UTC
Parallelism
62/100
Blocked
54%
Avg conflicts / tx
1.23
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #107,823,144 · 13 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
1w02w14w25w36w07w18w29w310w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66fc0764…05fd
0x34b655…2a6f
10 touches
10 conflicts
0xbbb11e9e…89bb
0x34b655…2a6f
10 touches
10 conflicts
0x90a021f0…f922
0x34b655…2a6f
10 touches
10 conflicts
0xba9f9225…2ead
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…001f
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0xf35dca9e…bd8f
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002f
0x1b6862…e19c
8 touches
6 conflicts
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 0x66fc076467…c305fd
Audit this contract →
← previous block·next block →recent activity