← previous blocknext block →recent activity
Analyzing
Block #91,423,916
34 transactions · 28 stateful · 2026-07-29 19:12:02 UTC
Parallelism
71/100
Blocked
61%
Avg conflicts / tx
1.82
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #91,423,916 · 34 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w18w29w311w016w317w418w520w621w722w825w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…004c
0x80c745…7210
14 touches
21 conflicts
0x00000000…004b
0x80c745…7210
14 touches
21 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0xb2195a0c…68ca
0x34b655…2a6f
10 touches
10 conflicts
0x6f1a10f8…5a04
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x6f58168d…ea24
0x34b655…2a6f
8 touches
6 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
21 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity