← previous blocknext block →recent activity
Analyzing
Block #91,771,637
9 transactions · 6 stateful · 2026-07-31 00:22:05 UTC
Parallelism
78/100
Blocked
17%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,771,637 · 9 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf51ec09c…b4a9
0x34b655…2a6f
4 touches
1 conflict
0x3c44e66b…bdb6
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x046740ca…4066
0x34b655…2a6f
2 touches
0 conflicts
0x0a8f8b9c…3046
0x34b655…2a6f
2 touches
0 conflicts
0x0c15f714…46ab
0x34b655…2a6f
2 touches
0 conflicts
0x2750196a…106d
0x34b655…2a6f
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 0xf51ec09cc1…a1b4a9
Audit this contract →
← previous block·next block →recent activity