← previous blocknext block →recent activity
Analyzing
Block #91,421,701
17 transactions · 17 stateful · 2026-07-29 19:00:49 UTC
Parallelism
59/100
Blocked
47%
Avg conflicts / tx
0.82
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #91,421,701 · 17 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
1w02w13w24w05w18w29w310w411w012w514w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf4f9cac7…fd98
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0x48cba2…b48b
6 touches
3 conflicts
0x4a078132…478a
0x34b655…2a6f
4 touches
1 conflict
0x4a6b3039…6a98
0x34b655…2a6f
4 touches
1 conflict
0x5502e1cc…3910
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x81561f70…fefd
0x34b655…2a6f
4 touches
1 conflict
0x91b0f8ed…6bd6
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
3 conflicts on slot 0xf4f9cac7d9…09fd98
Audit this contract →
← previous block·next block →recent activity