← previous blocknext block →recent activity
Analyzing
Block #91,799,095
10 transactions · 9 stateful · 2026-07-31 02:40:13 UTC
Parallelism
70/100
Blocked
44%
Avg conflicts / tx
0.7
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,799,095 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7bb8bdfc…f677
0x34b655…2a6f
6 touches
3 conflicts
0xfe72a59d…a607
0x34b655…2a6f
4 touches
1 conflict
0xb9834665…e363
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc014bcf3…3ac7
0x34b655…2a6f
4 touches
1 conflict
0xe4f11816…d1cd
0x34b655…2a6f
4 touches
1 conflict
0xe670c2b4…f61e
0x34b655…2a6f
4 touches
1 conflict
0xf973b772…9aec
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 0x7bb8bdfc9a…5cf677
Audit this contract →
← previous block·next block →recent activity