← previous blocknext block →recent activity
Analyzing
Block #105,683,678
20 transactions · 20 stateful · 2026-09-17 19:02:34 UTC
Parallelism
70/100
Blocked
40%
Avg conflicts / tx
1.05
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,683,678 · 20 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
1w05w16w211w212w313w414w415w518w019w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5eb6a5ed…acf8
0x34b655…2a6f
12 touches
15 conflicts
0xeb5b61a2…b2bc
0x34b655…2a6f
10 touches
10 conflicts
0x16959359…a041
0x34b655…2a6f
8 touches
6 conflicts
0x0efc210e…70ab
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x4e135144…4167
0x34b655…2a6f
4 touches
1 conflict
0x0463db49…5d05
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 0x5eb6a5ed5e…f8acf8
Audit this contract →
← previous block·next block →recent activity