← previous blocknext block →recent activity
Analyzing
Block #91,434,002
22 transactions · 20 stateful · 2026-07-29 20:03:35 UTC
Parallelism
82/100
Blocked
50%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,434,002 · 22 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w07w18w010w111w213w214w315w217w218w320w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08a39015…efa0
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xa0dca6bc…79b2
0x34b655…2a6f
6 touches
3 conflicts
0x38a74d2a…7782
0x34b655…2a6f
6 touches
3 conflicts
0x155e52ca…fac7
0x34b655…2a6f
4 touches
1 conflict
0x183615c5…5599
0x34b655…2a6f
4 touches
1 conflict
0x394157f0…7aae
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
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
6 conflicts on slot 0x08a39015ce…3fefa0
Audit this contract →
← previous block·next block →recent activity