← previous blocknext block →recent activity
Analyzing
Block #91,446,496
25 transactions · 23 stateful · 2026-07-29 21:06:26 UTC
Parallelism
84/100
Blocked
35%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,446,496 · 25 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w17w08w09w010w111w112w214w115w219w322w023w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x033cf007…136d
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x334aa47d…cac0
0x34b655…2a6f
6 touches
3 conflicts
0x33a24f73…b23a
0x34b655…2a6f
6 touches
3 conflicts
0x6b7e25db…9251
0x34b655…2a6f
6 touches
3 conflicts
0x76c067cb…119f
0x34b655…2a6f
6 touches
3 conflicts
0x7f9061c2…46d8
0x34b655…2a6f
6 touches
3 conflicts
0xa3ff1ab2…8ae3
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x033cf007c8…d2136d
Audit this contract →
← previous block·next block →recent activity