← previous blocknext block →recent activity
Analyzing
Block #91,549,791
10 transactions · 10 stateful · 2026-07-30 05:46:09 UTC
Parallelism
80/100
Blocked
40%
Avg conflicts / tx
0.5
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,549,791 · 10 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
2w03w14w07w18w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfcfe96e7…4a4d
0x34b655…2a6f
4 touches
1 conflict
0xdd3149e9…8a7d
0x34b655…2a6f
4 touches
1 conflict
0xf0c5be9f…e091
0x34b655…2a6f
4 touches
1 conflict
0x1b77e6f7…53d7
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x521a91b0…b4c9
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 0xfcfe96e723…fd4a4d
Audit this contract →
← previous block·next block →recent activity