← previous blocknext block →recent activity
Analyzing
Block #106,198,488
30 transactions · 26 stateful · 2026-09-19 14:15:58 UTC
Parallelism
73/100
Blocked
58%
Avg conflicts / tx
1.4
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,198,488 · 30 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
1w02w14w06w17w28w212w316w421w522w625w626w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa9de8bbd…02b4
0x34b655…2a6f
14 touches
21 conflicts
0x0c34d4e6…f241
0x34b655…2a6f
10 touches
10 conflicts
0xd8cadc0d…776e
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xa9a9d0e0…4087
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0002
0xf5b5f7…6d70
6 touches
3 conflicts
0x000bde1a…e123
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 0xa9de8bbd09…6802b4
Audit this contract →
← previous block·next block →recent activity