← previous blocknext block →recent activity
Analyzing
Block #91,822,748
24 transactions · 20 stateful · 2026-07-31 04:39:13 UTC
Parallelism
92/100
Blocked
10%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,822,748 · 24 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
1w02w116w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x329f2f7d…dcff
0x34b655…2a6f
4 touches
1 conflict
0x456b4779…5365
0x34b655…2a6f
4 touches
1 conflict
0x54d68470…4b32
0x34b655…2a6f
4 touches
1 conflict
0x58d00fbd…58e1
0x34b655…2a6f
4 touches
1 conflict
0xa457c06e…2f06
0x34b655…2a6f
4 touches
1 conflict
0x00000000…002f
0x1b6862…e19c
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity