← previous blocknext block →recent activity
Analyzing
Block #91,395,261
13 transactions · 13 stateful · 2026-07-29 16:47:25 UTC
Parallelism
85/100
Blocked
8%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,395,261 · 13 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
6w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x409d9cb9…36a8
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xefcdf197…96a2
0x34b655…2a6f
4 touches
1 conflict
0x149ea1fb…e34a
0x34b655…2a6f
2 touches
0 conflicts
0x17762848…51da
0x34b655…2a6f
2 touches
0 conflicts
0x18e900fa…07f4
0x34b655…2a6f
2 touches
0 conflicts
0x1af644dc…0822
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 0x409d9cb944…6136a8
Audit this contract →
← previous block·next block →recent activity