← previous blocknext block →recent activity
Analyzing
Block #91,549,551
12 transactions · 10 stateful · 2026-07-30 05:44:56 UTC
Parallelism
50/100
Blocked
60%
Avg conflicts / tx
1.33
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,549,551 · 12 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
1w02w15w06w17w28w39w410w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2504936d…39f3
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xac3e4969…39e9
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0029
0x1b6862…e19c
4 touches
1 conflict
0xd996735f…872f
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x146f0fd7…34d3
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 0x2504936d8b…5739f3
Audit this contract →
← previous block·next block →recent activity