← previous blocknext block →recent activity
Analyzing
Block #91,073,005
26 transactions · 25 stateful · 2026-07-28 13:45:08 UTC
Parallelism
69/100
Blocked
56%
Avg conflicts / tx
1.15
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #91,073,005 · 26 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w05w06w17w28w39w410w111w212w013w515w618w122w623w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x3e6302c8…64f5
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0x48cba2…b48b
6 touches
3 conflicts
0xda2ee2e7…968a
0x34b655…2a6f
6 touches
3 conflicts
0x20fb35c7…09c2
0x34b655…2a6f
6 touches
3 conflicts
0xa558e115…fc88
0x34b655…2a6f
6 touches
3 conflicts
0x08a39015…efa0
0x34b655…2a6f
6 touches
3 conflicts
0xc387ebf1…799e
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
10 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity