← previous blocknext block →recent activity
Analyzing
Block #106,467,158
16 transactions · 15 stateful · 2026-09-20 12:48:13 UTC
Parallelism
69/100
Blocked
53%
Avg conflicts / tx
0.69
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,467,158 · 16 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
1w02w13w25w27w111w213w314w415w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7462b8f2…6312
0x34b655…2a6f
6 touches
3 conflicts
0xfe890a5b…ac60
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0x810a3aa2…0227
0x34b655…2a6f
6 touches
3 conflicts
0x7fa77195…d46f
0x34b655…2a6f
6 touches
3 conflicts
0x1dc71894…1884
0x34b655…2a6f
6 touches
3 conflicts
0x27b85bff…02f7
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
3 conflicts on slot 0x7462b8f2c2…8d6312
Audit this contract →
← previous block·next block →recent activity