← previous blocknext block →recent activity
Analyzing
Block #91,259,602
19 transactions · 18 stateful · 2026-07-29 05:24:00 UTC
Parallelism
68/100
Blocked
39%
Avg conflicts / tx
0.58
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,259,602 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w15w27w011w112w216w317w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7ee74e97…55f1
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x0f2d78b1…7363
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x6fbc2e5a…e69c
0x34b655…2a6f
4 touches
1 conflict
0x20ff4a58…7c43
0x34b655…2a6f
4 touches
1 conflict
0x9392dae8…e1f0
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
3 conflicts on slot 0x7ee74e97a5…ef55f1
Audit this contract →
← previous block·next block →recent activity