← previous blocknext block →recent activity
Analyzing
Block #91,410,815
37 transactions · 35 stateful · 2026-07-29 18:06:01 UTC
Parallelism
60/100
Blocked
51%
Avg conflicts / tx
1.92
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #91,410,815 · 37 txs across 15 waves · depth 15
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
wave w14
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w16w07w18w29w310w411w512w613w714w818w1022w1133w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
18 touches
36 conflicts
0xebac0f82…a49c
0x34b655…2a6f
10 touches
10 conflicts
0x5fe7e126…6dd2
0x34b655…2a6f
8 touches
6 conflicts
0xfecb18c0…01ed
0x34b655…2a6f
8 touches
6 conflicts
0x2fd12b6c…02cc
0x34b655…2a6f
6 touches
3 conflicts
0x5502e1cc…3910
0x34b655…2a6f
6 touches
3 conflicts
0x772ab420…c2f6
0x34b655…2a6f
6 touches
3 conflicts
0x98d64054…e0f2
0x34b655…2a6f
6 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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity