← previous blocknext block →recent activity
Analyzing
Block #91,810,175
21 transactions · 17 stateful · 2026-07-31 03:35:58 UTC
Parallelism
71/100
Blocked
41%
Avg conflicts / tx
0.86
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,810,175 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w05w16w28w39w110w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd66696e0…0842
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xf1040e31…bfff
0x34b655…2a6f
10 touches
10 conflicts
0x50c388ce…aee7
0x34b655…2a6f
10 touches
10 conflicts
0xef5959a3…2a2f
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 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
15 conflicts on slot 0xd66696e0dc…230842
Audit this contract →
← previous block·next block →recent activity