← previous blocknext block →recent activity
Analyzing
Block #91,411,008
18 transactions · 17 stateful · 2026-07-29 18:07:00 UTC
Parallelism
78/100
Blocked
24%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,411,008 · 18 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
5w07w08w111w112w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbc4e7b49…3d2d
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xf973b772…9aec
0x34b655…2a6f
4 touches
1 conflict
0xf9cae879…1023
0x34b655…2a6f
4 touches
1 conflict
0x6aea3f64…bb1f
0x34b655…2a6f
4 touches
1 conflict
0x6c3907cd…5ac0
0x34b655…2a6f
4 touches
1 conflict
0x7bb8bdfc…f677
0x34b655…2a6f
4 touches
1 conflict
0xb9834665…e363
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 0xbc4e7b4911…633d2d
Audit this contract →
← previous block·next block →recent activity