← previous blocknext block →recent activity
Analyzing
Block #91,127,737
10 transactions · 9 stateful · 2026-07-28 18:20:34 UTC
Parallelism
70/100
Blocked
44%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,127,737 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w27w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49887f7e…9e7c
0x34b655…2a6f
6 touches
3 conflicts
0x4a39a2a4…857b
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x8cd684d0…c3cb
0x34b655…2a6f
4 touches
1 conflict
0x1408a100…f721
0x34b655…2a6f
2 touches
0 conflicts
0x145b9bbf…e50e
0x34b655…2a6f
2 touches
0 conflicts
0x2508461a…b483
0x34b655…2a6f
2 touches
0 conflicts
0x6d9d9661…73f0
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
3 conflicts on slot 0x49887f7ea5…989e7c
Audit this contract →
← previous block·next block →recent activity