← previous blocknext block →recent activity
Analyzing
Block #106,420,876
22 transactions · 22 stateful · 2026-09-20 08:55:14 UTC
Parallelism
68/100
Blocked
59%
Avg conflicts / tx
1.59
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,420,876 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w16w28w310w212w413w517w318w419w520w621w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60be5cbc…7218
0x34b655…2a6f
14 touches
21 conflicts
0xbe9d1d23…3de2
0x34b655…2a6f
10 touches
10 conflicts
0x524f0872…0d12
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x0dd3d3cd…7281
0x34b655…2a6f
6 touches
3 conflicts
0x310a7246…2dcb
0x34b655…2a6f
6 touches
3 conflicts
0x4118bd12…924a
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
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
21 conflicts on slot 0x60be5cbc32…9f7218
Audit this contract →
← previous block·next block →recent activity