← previous blocknext block →recent activity
Analyzing
Block #106,469,912
22 transactions · 20 stateful · 2026-09-20 13:02:05 UTC
Parallelism
64/100
Blocked
55%
Avg conflicts / tx
1.27
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,469,912 · 22 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
1w02w03w14w05w18w29w310w411w512w114w415w520w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x91e7eb48…7365
0x34b655…2a6f
12 touches
15 conflicts
0xecd87a39…d9c5
0x34b655…2a6f
8 touches
6 conflicts
0xba33378a…f1df
0x34b655…2a6f
8 touches
6 conflicts
0xcd9ba26b…108d
0x34b655…2a6f
8 touches
6 conflicts
0xea2a1d1b…4115
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0xad862891…5d02
0x34b655…2a6f
6 touches
3 conflicts
0x5655f5c3…6b75
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
15 conflicts on slot 0x91e7eb48ed…557365
Audit this contract →
← previous block·next block →recent activity