← previous blocknext block →recent activity
Analyzing
Block #91,100,213
21 transactions · 21 stateful · 2026-07-28 16:02:07 UTC
Parallelism
52/100
Blocked
52%
Avg conflicts / tx
2.62
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #91,100,213 · 21 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
4w05w06w18w19w111w212w313w414w515w616w717w818w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x737acb78…fce8
0x34b655…2a6f
18 touches
36 conflicts
0xbde524f4…43bf
0x34b655…2a6f
18 touches
36 conflicts
0xac2a0273…721b
0x34b655…2a6f
18 touches
36 conflicts
0xce06a0f7…efef
0x34b655…2a6f
14 touches
21 conflicts
0xd3555fb4…5eba
0x34b655…2a6f
9 touches
10 conflicts
0xab2b1605…716c
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x2ea57368…3ae6
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
36 conflicts on slot 0x737acb7813…fafce8
Audit this contract →
← previous block·next block →recent activity