← previous blocknext block →recent activity
Analyzing
Block #91,242,543
19 transactions · 19 stateful · 2026-07-29 03:58:04 UTC
Parallelism
68/100
Blocked
42%
Avg conflicts / tx
1.32
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,242,543 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w05w16w17w28w39w411w114w516w017w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xa779293b…5e59
0x34b655…2a6f
10 touches
10 conflicts
0x6e6b8ec7…2197
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xbd765aea…6fda
0x34b655…2a6f
6 touches
3 conflicts
0x8fe2c648…84a8
0x34b655…2a6f
4 touches
1 conflict
0xa4041c86…a637
0x34b655…2a6f
4 touches
1 conflict
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity