← previous blocknext block →recent activity
Analyzing
Block #91,106,168
33 transactions · 28 stateful · 2026-07-28 16:32:04 UTC
Parallelism
67/100
Blocked
54%
Avg conflicts / tx
1.24
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #91,106,168 · 33 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w08w09w110w211w312w413w515w516w621w622w223w726w127w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0xcc351d6d…256b
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xb9834665…e363
0x34b655…2a6f
6 touches
3 conflicts
0x13306c72…fb14
0x34b655…2a6f
6 touches
3 conflicts
0x4a6b3039…6a98
0x34b655…2a6f
4 touches
1 conflict
0x5222dd71…68ca
0x34b655…2a6f
4 touches
1 conflict
0x7dd8477e…ae46
0x34b655…2a6f
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
15 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity