← previous blocknext block →recent activity
Analyzing
Block #91,771,399
7 transactions · 5 stateful · 2026-07-31 00:20:53 UTC
Parallelism
71/100
Blocked
20%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,771,399 · 7 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x310afe2c…83e1
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0327b211…2766
0x34b655…2a6f
2 touches
0 conflicts
0x0d7d817f…6eee
0x34b655…2a6f
2 touches
0 conflicts
0x2c140037…b5ae
0x34b655…2a6f
2 touches
0 conflicts
0x2d651956…12e8
0x34b655…2a6f
2 touches
0 conflicts
0x31b39922…1e66
0x34b655…2a6f
2 touches
0 conflicts
0x3cb7ee74…b8a5
0x34b655…2a6f
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 0x310afe2cd5…d683e1
Audit this contract →
← previous block·next block →recent activity