← previous blocknext block →recent activity
Analyzing
Block #91,132,634
13 transactions · 13 stateful · 2026-07-28 18:45:12 UTC
Parallelism
39/100
Blocked
54%
Avg conflicts / tx
2.15
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #91,132,634 · 13 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w16w27w38w49w510w611w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x737acb78…fce8
0x34b655…2a6f
16 touches
28 conflicts
0xac2a0273…721b
0x34b655…2a6f
16 touches
28 conflicts
0xce06a0f7…efef
0x34b655…2a6f
12 touches
15 conflicts
0xbde524f4…43bf
0x34b655…2a6f
12 touches
15 conflicts
0xd676e291…3ecf
0x34b655…2a6f
8 touches
6 conflicts
0x50ea66a4…0b5d
0x34b655…2a6f
6 touches
3 conflicts
0xf0349af4…33a6
0x34b655…2a6f
6 touches
3 conflicts
0xaee57a90…cfb9
0x34b655…2a6f
5 touches
3 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
28 conflicts on slot 0x737acb7813…fafce8
Audit this contract →
← previous block·next block →recent activity