← previous blocknext block →recent activity
Analyzing
Block #107,823,128
13 transactions · 13 stateful · 2026-09-25 06:36:38 UTC
Parallelism
69/100
Blocked
23%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #107,823,128 · 13 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
7w08w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6a20ad66…fc63
0x34b655…2a6f
8 touches
6 conflicts
0xba9f9225…2ead
0x34b655…2a6f
8 touches
6 conflicts
0x66fc0764…05fd
0x34b655…2a6f
8 touches
6 conflicts
0x90a021f0…f922
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x422cccbc…9b18
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x7c80d7be…b7dc
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 0x6a20ad6681…eafc63
Audit this contract →
← previous block·next block →recent activity