← previous blocknext block →recent activity
Analyzing
Block #105,853,338
22 transactions · 22 stateful · 2026-09-18 09:17:52 UTC
Parallelism
82/100
Blocked
32%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,853,338 · 22 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w16w17w29w213w317w018w120w021w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd9b57567…1f3e
0x34b655…2a6f
6 touches
3 conflicts
0xbc8fb280…76a3
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x48828733…fd48
0x34b655…2a6f
4 touches
1 conflict
0x739123da…57f3
0x34b655…2a6f
4 touches
1 conflict
0x7a3d5e6f…7864
0x34b655…2a6f
4 touches
1 conflict
0x7c2b0f0e…4933
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
3 conflicts on slot 0xd9b57567a6…931f3e
Audit this contract →
← previous block·next block →recent activity