← previous blocknext block →recent activity
Analyzing
Block #91,956,516
42 transactions · 38 stateful · 2026-07-31 15:52:13 UTC
Parallelism
67/100
Blocked
63%
Avg conflicts / tx
2.17
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #91,956,516 · 42 txs across 14 waves · depth 14
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w06w07w18w29w310w411w512w613w714w820w823w124w226w327w428w533w734w1038w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
18 touches
36 conflicts
0xca2926e0…61b5
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x43fab434…896f
0xa6afd3…d132
8 touches
6 conflicts
0x1aaf4996…65ec
0x34b655…2a6f
8 touches
6 conflicts
0xa56e54d0…2d39
0x34b655…2a6f
8 touches
6 conflicts
0xab5ba139…ea6f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 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
36 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity