← previous blocknext block →recent activity
Analyzing
Block #91,273,288
37 transactions · 34 stateful · 2026-07-29 06:33:33 UTC
Parallelism
62/100
Blocked
65%
Avg conflicts / tx
2.19
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #91,273,288 · 37 txs across 14 waves · depth 14
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w19w010w111w012w113w216w217w318w319w220w321w422w323w424w526w527w629w830w931w1034w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0xebac0f82…a49c
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0x40c49f…2af0
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x76d1e78d…7877
0x40c49f…2af0
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x326a02b5…8dad
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
36 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity