← previous blocknext block →recent activity
Analyzing
Block #91,129,614
24 transactions · 23 stateful · 2026-07-28 18:30:00 UTC
Parallelism
58/100
Blocked
48%
Avg conflicts / tx
1.38
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #91,129,614 · 24 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
1w02w14w05w17w28w39w410w511w616w719w820w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0xd676e291…3ecf
0x34b655…2a6f
8 touches
6 conflicts
0x1514a0fb…d697
0x34b655…2a6f
6 touches
3 conflicts
0x2c66ecd1…f41d
0x34b655…2a6f
6 touches
3 conflicts
0xd9461b7e…31bc
0x34b655…2a6f
6 touches
3 conflicts
0x0f2d78b1…7363
0x34b655…2a6f
6 touches
3 conflicts
0x5cc0e9c8…3ae6
0x34b655…2a6f
6 touches
3 conflicts
0xb9c84c75…b267
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
15 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity