← previous blocknext block →recent activity
Analyzing
Block #107,823,124
23 transactions · 20 stateful · 2026-09-25 06:36:36 UTC
Parallelism
65/100
Blocked
50%
Avg conflicts / tx
1.35
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #107,823,124 · 23 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w08w110w011w112w213w314w415w516w617w722w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66fc0764…05fd
0x34b655…2a6f
16 touches
28 conflicts
0x6a20ad66…fc63
0x34b655…2a6f
16 touches
28 conflicts
0x90a021f0…f922
0x34b655…2a6f
14 touches
21 conflicts
0xba9f9225…2ead
0x34b655…2a6f
14 touches
21 conflicts
0xbbb11e9e…89bb
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x422cccbc…9b18
0x34b655…2a6f
8 touches
6 conflicts
0x7c80d7be…b7dc
0x34b655…2a6f
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
28 conflicts on slot 0x66fc076467…c305fd
Audit this contract →
← previous block·next block →recent activity