← previous blocknext block →recent activity
Analyzing
Block #91,764,480
19 transactions · 16 stateful · 2026-07-30 23:46:05 UTC
Parallelism
63/100
Blocked
38%
Avg conflicts / tx
1.11
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #91,764,480 · 19 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
5w06w17w29w310w415w517w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8252706a…7ca5
0x34b655…2a6f
14 touches
21 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x02ebc44a…9fbb
0x34b655…2a6f
4 touches
1 conflict
0x68d9d4e4…91b6
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
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
21 conflicts on slot 0x8252706a8a…797ca5
Audit this contract →
← previous block·next block →recent activity