← previous blocknext block →recent activity
Analyzing
Block #91,385,444
18 transactions · 16 stateful · 2026-07-29 15:58:03 UTC
Parallelism
72/100
Blocked
31%
Avg conflicts / tx
0.39
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,385,444 · 18 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
2w03w15w26w310w413w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x06d0bea9…b922
0x34b655…2a6f
4 touches
1 conflict
0x07d8b1e8…78c6
0x34b655…2a6f
4 touches
1 conflict
0x28ceceef…ecc2
0x34b655…2a6f
4 touches
1 conflict
0x3244bc68…5263
0x34b655…2a6f
4 touches
1 conflict
0x37ab49be…3b8b
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x5af098c7…4806
0x34b655…2a6f
4 touches
1 conflict
0x5af098c7…4807
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
1 conflict on slot 0x06d0bea92d…ecb922
Audit this contract →
← previous block·next block →recent activity