← previous blocknext block →recent activity
Analyzing
Block #106,477,446
26 transactions · 22 stateful · 2026-09-20 13:39:59 UTC
Parallelism
77/100
Blocked
36%
Avg conflicts / tx
0.69
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,477,446 · 26 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
3w04w05w16w07w19w011w115w117w218w320w421w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcd9ba26b…108d
0x34b655…2a6f
12 touches
15 conflicts
0x2836d18c…d85c
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x1b25f260…c429
0x34b655…2a6f
4 touches
1 conflict
0x810a3aa2…0227
0x34b655…2a6f
4 touches
1 conflict
0x8552720e…47b8
0x34b655…2a6f
4 touches
1 conflict
0xa3ed5a09…c6d3
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 0xcd9ba26bf8…62108d
Audit this contract →
← previous block·next block →recent activity