← previous blocknext block →recent activity
Analyzing
Block #91,569,925
13 transactions · 10 stateful · 2026-07-30 07:27:24 UTC
Parallelism
69/100
Blocked
40%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,569,925 · 13 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w26w312w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x76c49694…51b3
0x34b655…2a6f
6 touches
3 conflicts
0xdd8e5705…17d6
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4e9b56fe…6464
0x34b655…2a6f
4 touches
1 conflict
0x5af098c7…4806
0x34b655…2a6f
4 touches
1 conflict
0x5af098c7…4807
0x34b655…2a6f
4 touches
1 conflict
0x7e1faa73…bfbf
0x34b655…2a6f
4 touches
1 conflict
0x9ef0b0f7…2508
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 0x76c496940e…2c51b3
Audit this contract →
← previous block·next block →recent activity