← previous blocknext block →recent activity
Analyzing
Block #105,575,337
16 transactions · 14 stateful · 2026-09-17 09:57:11 UTC
Parallelism
88/100
Blocked
21%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #105,575,337 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5d28bce…c32c
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x045532dd…4b7d
0x34b655…2a6f
4 touches
1 conflict
0x79ec4509…1f61
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
0x34b655…2a6f
4 touches
1 conflict
0x04d4f30d…4dfb
0x34b655…2a6f
2 touches
0 conflicts
0x0d5a9976…9da7
0x34b655…2a6f
2 touches
0 conflicts
0x24d6bacf…5316
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xf5d28bce28…fbc32c
Audit this contract →
← previous block·next block →recent activity