← previous blocknext block →recent activity
Analyzing
Block #105,856,318
20 transactions · 17 stateful · 2026-09-18 09:32:52 UTC
Parallelism
80/100
Blocked
35%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,856,318 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w06w19w111w212w315w218w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa93fef74…94b3
0x37db7f…ec7b
8 touches
6 conflicts
0xdbcc4ab8…2aba
0x37db7f…ec7b
8 touches
6 conflicts
0xe3e67fe3…e754
0x37db7f…ec7b
8 touches
6 conflicts
0x21d22421…0b7a
0x34b655…2a6f
8 touches
6 conflicts
0x4681609f…6493
0x34b655…2a6f
8 touches
6 conflicts
0x65e795ca…0320
0x34b655…2a6f
8 touches
6 conflicts
0xac206e47…ef7d
0x34b655…2a6f
8 touches
6 conflicts
0xb34a93c7…c8ae
0x34b655…2a6f
8 touches
6 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: 0x37db7fbf…3eec7b
6 conflicts on slot 0xa93fef7411…4194b3
Audit this contract →
← previous block·next block →recent activity