← previous blocknext block →recent activity
Analyzing
Block #91,961,164
14 transactions · 14 stateful · 2026-07-31 16:15:36 UTC
Parallelism
50/100
Blocked
43%
Avg conflicts / tx
1.21
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #91,961,164 · 14 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w07w18w29w310w411w512w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x8a5ced1c…3b29
0x34b655…2a6f
6 touches
3 conflicts
0x5d3bb355…4549
0x34b655…2a6f
6 touches
3 conflicts
0x38021f8c…3ec8
0x34b655…2a6f
6 touches
3 conflicts
0x13a157e0…215b
0x34b655…2a6f
6 touches
3 conflicts
0x9927f045…9256
0x34b655…2a6f
4 touches
1 conflict
0x9aea124d…de52
0x34b655…2a6f
4 touches
1 conflict
0x9cc81330…2fcf
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
15 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity