← previous blocknext block →recent activity
Analyzing
Block #91,969,296
11 transactions · 11 stateful · 2026-07-31 16:56:30 UTC
Parallelism
82/100
Blocked
18%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,969,296 · 11 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
2w05w06w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x74e46435…fdcd
0x34b655…2a6f
4 touches
1 conflict
0xa20a130c…5d59
0x34b655…2a6f
4 touches
1 conflict
0xa4e9800f…4ab1
0x34b655…2a6f
4 touches
1 conflict
0x266f8846…49fd
0x065c9d…c394
2 touches
0 conflicts
0x3267513b…6853
0x065c9d…c394
2 touches
0 conflicts
0x8aedc364…ff2f
0x065c9d…c394
2 touches
0 conflicts
0xa9252bc3…2322
0x065c9d…c394
2 touches
0 conflicts
0xd6e941a1…5bde
0x065c9d…c394
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 0x74e4643549…2bfdcd
Audit this contract →
← previous block·next block →recent activity