← previous blocknext block →recent activity
Analyzing
Block #91,780,490
13 transactions · 13 stateful · 2026-07-31 01:06:38 UTC
Parallelism
77/100
Blocked
31%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,780,490 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w16w17w28w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1e137b39…bae2
0x34b655…2a6f
6 touches
3 conflicts
0x9a8af3c2…e4ae
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xca529dbd…dc62
0x34b655…2a6f
4 touches
1 conflict
0xd3d2b624…594f
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x4e970d38…d1c4
0x34b655…2a6f
4 touches
1 conflict
0x63bed776…8d4a
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
3 conflicts on slot 0x1e137b391d…b2bae2
Audit this contract →
← previous block·next block →recent activity