← previous blocknext block →recent activity
Analyzing
Block #91,087,808
25 transactions · 24 stateful · 2026-07-28 14:59:40 UTC
Parallelism
72/100
Blocked
42%
Avg conflicts / tx
0.72
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #91,087,808 · 25 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
1w02w13w05w16w27w38w49w513w216w619w020w123w024w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x620b761c…270e
0x34b655…2a6f
10 touches
10 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x8c6d9bf1…a25a
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x4b7e216a…7258
0x34b655…2a6f
4 touches
1 conflict
0x4b7e216a…7259
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity