← previous blocknext block →recent activity
Analyzing
Block #91,809,233
17 transactions · 17 stateful · 2026-07-31 03:31:14 UTC
Parallelism
59/100
Blocked
41%
Avg conflicts / tx
1.18
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #91,809,233 · 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
2w04w15w27w39w410w511w614w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x47b56a32…dcf4
0x34b655…2a6f
12 touches
15 conflicts
0x231ccc13…a7c6
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6426
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xa4e9800f…4ab0
0x34b655…2a6f
6 touches
3 conflicts
0x98b8e5ef…bda4
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 0x47b56a3281…b2dcf4
Audit this contract →
← previous block·next block →recent activity