← previous blocknext block →recent activity
Analyzing
Block #91,570,518
22 transactions · 17 stateful · 2026-07-30 07:30:23 UTC
Parallelism
86/100
Blocked
24%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,570,518 · 22 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
1w08w09w110w114w015w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0a0ac643…b698
0x34b655…2a6f
4 touches
1 conflict
0xcca11bc9…3470
0x34b655…2a6f
4 touches
1 conflict
0xda27c764…7fab
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x1b6c23a0…723b
0x851145…3f07
4 touches
1 conflict
0x2a628ea8…5918
0x851145…3f07
4 touches
1 conflict
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0x3a3e7727…36c5
0x2b46c0…1669
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 0x0a0ac643cd…c2b698
Audit this contract →
← previous block·next block →recent activity