← previous blocknext block →recent activity
Analyzing
Block #88,365,763
22 transactions · 21 stateful · 2026-07-17 14:43:46 UTC
Parallelism
82/100
Blocked
48%
Avg conflicts / tx
0.68
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #88,365,763 · 22 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
1w02w15w06w17w28w39w010w112w013w114w115w216w017w219w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x3ef0952c…762d
0x34b655…2a6f
6 touches
3 conflicts
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xbc2d4622…e7e9
0x34b655…2a6f
4 touches
1 conflict
0xd2d3fe13…b827
0x34b655…2a6f
4 touches
1 conflict
0xd2d3fe13…b828
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
6 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity