← previous blocknext block →recent activity
Analyzing
Block #91,271,773
21 transactions · 18 stateful · 2026-07-29 06:25:55 UTC
Parallelism
76/100
Blocked
56%
Avg conflicts / tx
0.71
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,271,773 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w15w06w18w09w110w211w312w113w214w317w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0xdd190722…ecae
0x34b655…2a6f
6 touches
3 conflicts
0x95dd1dda…bc0e
0x34b655…2a6f
6 touches
3 conflicts
0xf28a9fc2…05e4
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x446e4f62…f7b6
0x34b655…2a6f
4 touches
1 conflict
0x451d616a…0fe5
0x34b655…2a6f
4 touches
1 conflict
0x55cf4758…265c
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
6 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity