← previous blocknext block →recent activity
Analyzing
Block #106,367,470
24 transactions · 23 stateful · 2026-09-20 04:26:28 UTC
Parallelism
75/100
Blocked
52%
Avg conflicts / tx
1.13
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,367,470 · 24 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
1w02w13w05w06w17w08w19w213w115w216w317w418w120w421w523w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb1abac7e…cb5b
0x34b655…2a6f
12 touches
15 conflicts
0xe8058ec4…ebac
0x34b655…2a6f
8 touches
6 conflicts
0x2130a548…c1de
0x34b655…2a6f
8 touches
6 conflicts
0x0463db49…5d05
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x4118bd12…924a
0x34b655…2a6f
6 touches
3 conflicts
0xc8f755b6…7b04
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 0xb1abac7e42…85cb5b
Audit this contract →
← previous block·next block →recent activity