← previous blocknext block →recent activity
Analyzing
Block #91,100,470
19 transactions · 17 stateful · 2026-07-28 16:03:24 UTC
Parallelism
63/100
Blocked
41%
Avg conflicts / tx
0.79
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #91,100,470 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w06w17w28w39w410w512w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x99701186…1cbf
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xf2b37bf3…5515
0x34b655…2a6f
6 touches
3 conflicts
0x77722039…2e5c
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
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
6 conflicts on slot 0x997011860a…ad1cbf
Audit this contract →
← previous block·next block →recent activity