← previous blocknext block →recent activity
Analyzing
Block #91,444,845
27 transactions · 18 stateful · 2026-07-29 20:58:08 UTC
Parallelism
81/100
Blocked
33%
Avg conflicts / tx
0.37
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,444,845 · 27 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w07w112w014w116w217w323w024w425w026w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa3bcc43f…d059
0x34b655…2a6f
6 touches
3 conflicts
0xdeaa385f…6b8b
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001f
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002f
0x1b6862…e19c
4 touches
1 conflict
0xd5a25205…645e
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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 0xa3bcc43f14…6cd059
Audit this contract →
← previous block·next block →recent activity