← previous blocknext block →recent activity
Analyzing
Block #88,363,877
25 transactions · 23 stateful · 2026-07-17 14:30:55 UTC
Parallelism
68/100
Blocked
35%
Avg conflicts / tx
0.84
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #88,363,877 · 25 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w06w17w29w310w014w417w020w521w622w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2d651956…12e8
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x1e166a45…98a7
0x34b655…2a6f
6 touches
3 conflicts
0x3ef0952c…762d
0x34b655…2a6f
6 touches
3 conflicts
0x2b5cb9f0…1d10
0x34b655…2a6f
4 touches
1 conflict
0x15c9b5bf…f732
0x34b655…2a6f
4 touches
1 conflict
0x2f461725…5ab2
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 0x2d65195682…4112e8
Audit this contract →
← previous block·next block →recent activity