← previous blocknext block →recent activity
Analyzing
Block #91,384,994
17 transactions · 16 stateful · 2026-07-29 15:55:47 UTC
Parallelism
59/100
Blocked
69%
Avg conflicts / tx
1.71
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #91,384,994 · 17 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w26w37w48w39w410w412w415w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x07d8b1e8…78c6
0x34b655…2a6f
8 touches
6 conflicts
0xb4e0a934…5fc7
0x34b655…2a6f
6 touches
3 conflicts
0x28ceceef…ecc2
0x34b655…2a6f
6 touches
3 conflicts
0x36a76bd2…1fb0
0x34b655…2a6f
6 touches
3 conflicts
0x6767539b…f211
0x34b655…2a6f
6 touches
3 conflicts
0x63b74d88…b6ca
0x34b655…2a6f
4 touches
1 conflict
0x08636046…e60f
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