← previous blocknext block →recent activity
Analyzing
Block #105,849,719
18 transactions · 18 stateful · 2026-09-18 08:59:39 UTC
Parallelism
72/100
Blocked
28%
Avg conflicts / tx
0.72
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,849,719 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w19w212w313w416w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x21ea8013…b07a
0x34b655…2a6f
10 touches
10 conflicts
0x5ce41e7b…247b
0x34b655…2a6f
8 touches
6 conflicts
0x2827ae77…4368
0x34b655…2a6f
8 touches
6 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
4 touches
1 conflict
0x43e3decb…be40
0x34b655…2a6f
4 touches
1 conflict
0x7c8cf338…6e72
0x34b655…2a6f
4 touches
1 conflict
0xbc8fb280…76a3
0x34b655…2a6f
4 touches
1 conflict
0xc10b903d…2f54
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
10 conflicts on slot 0x21ea8013c0…84b07a
Audit this contract →
← previous block·next block →recent activity