← previous blocknext block →recent activity
Analyzing
Block #91,397,424
9 transactions · 8 stateful · 2026-07-29 16:58:19 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,397,424 · 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
4w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdd1cdd51…c982
0x34b655…2a6f
4 touches
1 conflict
0x327c57dd…836d
0x34b655…2a6f
4 touches
1 conflict
0xbe9baf16…df37
0x34b655…2a6f
4 touches
1 conflict
0x049041f8…3cab
0x34b655…2a6f
2 touches
0 conflicts
0x3c1ab6b5…4674
0x34b655…2a6f
2 touches
0 conflicts
0x3c1cd3a5…4b3e
0x34b655…2a6f
2 touches
0 conflicts
0x49887f7e…9e7c
0x34b655…2a6f
2 touches
0 conflicts
0x548145a9…cfce
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 0xdd1cdd5148…87c982
Audit this contract →
← previous block·next block →recent activity