← previous blocknext block →recent activity
Analyzing
Block #91,549,773
14 transactions · 12 stateful · 2026-07-30 05:46:03 UTC
Parallelism
57/100
Blocked
42%
Avg conflicts / tx
1.07
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,549,773 · 14 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w27w38w412w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc58c80b…ff79
0x34b655…2a6f
12 touches
15 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
8 touches
6 conflicts
0x3726966a…669d
0x34b655…2a6f
4 touches
1 conflict
0x3accd47f…d16e
0x34b655…2a6f
4 touches
1 conflict
0x49f75237…44f4
0x34b655…2a6f
4 touches
1 conflict
0x4ca1448c…9de6
0x34b655…2a6f
4 touches
1 conflict
0x681f6633…7d9e
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
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
15 conflicts on slot 0xcc58c80b6c…80ff79
Audit this contract →
← previous block·next block →recent activity