← previous blocknext block →recent activity
Analyzing
Block #105,841,219
18 transactions · 17 stateful · 2026-09-18 08:16:43 UTC
Parallelism
67/100
Blocked
41%
Avg conflicts / tx
0.94
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,841,219 · 18 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
1w02w08w19w010w111w212w313w414w517w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1659f2d1…b734
0x34b655…2a6f
12 touches
15 conflicts
0x0463db49…5d05
0x34b655…2a6f
8 touches
6 conflicts
0xead15497…1dbe
0x34b655…2a6f
8 touches
6 conflicts
0x81ca8c9e…28cb
0x34b655…2a6f
8 touches
6 conflicts
0x5fad6fee…7714
0x34b655…2a6f
8 touches
6 conflicts
0xf71016c7…5c7c
0x34b655…2a6f
6 touches
3 conflicts
0x3ca49f3f…b79f
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 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 0x1659f2d172…44b734
Audit this contract →
← previous block·next block →recent activity