← previous blocknext block →recent activity
Analyzing
Block #107,823,132
16 transactions · 15 stateful · 2026-09-25 06:36:39 UTC
Parallelism
63/100
Blocked
53%
Avg conflicts / tx
1.13
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #107,823,132 · 16 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
3w05w17w08w19w210w311w412w513w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66fc0764…05fd
0x34b655…2a6f
12 touches
15 conflicts
0xba9f9225…2ead
0x34b655…2a6f
12 touches
15 conflicts
0x6a20ad66…fc63
0x34b655…2a6f
12 touches
15 conflicts
0x90a021f0…f922
0x34b655…2a6f
8 touches
6 conflicts
0x7c80d7be…b7dc
0x34b655…2a6f
6 touches
3 conflicts
0x422cccbc…9b18
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 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
15 conflicts on slot 0x66fc076467…c305fd
Audit this contract →
← previous block·next block →recent activity