← previous blocknext block →recent activity
Analyzing
Block #105,683,718
17 transactions · 17 stateful · 2026-09-17 19:02:46 UTC
Parallelism
65/100
Blocked
35%
Avg conflicts / tx
0.94
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,683,718 · 17 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
3w04w18w010w212w313w414w515w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeb5b61a2…b2bc
0x34b655…2a6f
10 touches
10 conflicts
0x04c65c08…63c2
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x14c20295…4d9e
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4e2d2643…b877
0x34b655…2a6f
4 touches
1 conflict
0x6a9ce11b…a0d1
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 0xeb5b61a29c…4fb2bc
Audit this contract →
← previous block·next block →recent activity