← previous blocknext block →recent activity
Analyzing
Block #91,423,890
12 transactions · 12 stateful · 2026-07-29 19:11:54 UTC
Parallelism
58/100
Blocked
42%
Avg conflicts / tx
0.92
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,423,890 · 12 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
1w02w13w27w38w410w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3d158563…8713
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x48b13e5e…3c2a
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xb4b1158e…aaef
0x34b655…2a6f
6 touches
3 conflicts
0xa8fc95a0…d6b9
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x02ed4afa…b107
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 0x3d1585630c…178713
Audit this contract →
← previous block·next block →recent activity