← previous blocknext block →recent activity
Analyzing
Block #91,543,842
9 transactions · 8 stateful · 2026-07-30 05:16:13 UTC
Parallelism
78/100
Blocked
13%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,543,842 · 9 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca608d0c…f23b
0x34b655…2a6f
4 touches
1 conflict
0x8fb50369…d3d2
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x0a2c05f7…8716
0x065c9d…c394
2 touches
0 conflicts
0x3e93957d…3e6a
0x065c9d…c394
2 touches
0 conflicts
0xd0af7a14…82ce
0x065c9d…c394
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x45f562b2…9294
0x2b46c0…1669
2 touches
0 conflicts
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
1 conflict on slot 0xca608d0ccc…6ff23b
Audit this contract →
← previous block·next block →recent activity