← previous blocknext block →recent activity
Analyzing
Block #105,618,757
20 transactions · 19 stateful · 2026-09-17 13:35:45 UTC
Parallelism
70/100
Blocked
42%
Avg conflicts / tx
1.05
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,618,757 · 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
1w04w05w16w27w38w413w515w116w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1bf239bd…46ad
0x34b655…2a6f
12 touches
15 conflicts
0x24b6091e…d294
0x34b655…2a6f
10 touches
10 conflicts
0x25eb7079…cb76
0x34b655…2a6f
10 touches
10 conflicts
0x2d38ef49…2bae
0x34b655…2a6f
10 touches
10 conflicts
0xb8dc136f…fb16
0xc8689a…ee79
10 touches
10 conflicts
0xaf59c69d…c904
0x37db7f…ec7b
10 touches
10 conflicts
0xf99548c6…30b3
0x37db7f…ec7b
10 touches
10 conflicts
0x0ce1cf3f…c7f4
0x34b655…2a6f
10 touches
10 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: Perpl
15 conflicts on slot 0x1bf239bde7…4d46ad
Audit this contract →
← previous block·next block →recent activity