← previous blocknext block →recent activity
Analyzing
Block #91,545,176
16 transactions · 15 stateful · 2026-07-30 05:22:56 UTC
Parallelism
69/100
Blocked
47%
Avg conflicts / tx
0.88
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,545,176 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w17w28w311w412w214w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x70b7b52e…7744
0x34b655…2a6f
8 touches
6 conflicts
0x70b7b52e…7743
0x34b655…2a6f
8 touches
6 conflicts
0x033cf007…136d
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x5e1a7839…33e2
0x34b655…2a6f
5 touches
3 conflicts
0xa940f3a4…c5e8
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
6 conflicts on slot 0x70b7b52e5b…0a7744
Audit this contract →
← previous block·next block →recent activity