← previous blocknext block →recent activity
Analyzing
Block #106,421,318
22 transactions · 20 stateful · 2026-09-20 08:57:27 UTC
Parallelism
55/100
Blocked
60%
Avg conflicts / tx
1.32
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,421,318 · 22 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w27w19w310w412w513w614w715w816w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0df715f3…1601
0x34b655…2a6f
10 touches
10 conflicts
0x5e1c23e9…4f81
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x1b25f260…c429
0x34b655…2a6f
6 touches
3 conflicts
0x7ed0f99d…6029
0x34b655…2a6f
6 touches
3 conflicts
0x9dd0a735…4d04
0x34b655…2a6f
6 touches
3 conflicts
0xbe9d1d23…3de2
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
10 conflicts on slot 0x0df715f30f…1e1601
Audit this contract →
← previous block·next block →recent activity