← previous blocknext block →recent activity
Analyzing
Block #91,140,170
10 transactions · 9 stateful · 2026-07-28 19:23:06 UTC
Parallelism
60/100
Blocked
33%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,140,170 · 10 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w05w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd2e35622…f491
0x34b655…2a6f
6 touches
3 conflicts
0xffc26b06…715f
0x34b655…2a6f
4 touches
1 conflict
0x41e3f022…1f03
0x34b655…2a6f
4 touches
1 conflict
0x4a6b3039…6a98
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xeb067536…4ccf
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 0xd2e3562276…b0f491
Audit this contract →
← previous block·next block →recent activity