← previous blocknext block →recent activity
Analyzing
Block #88,352,340
14 transactions · 13 stateful · 2026-07-17 13:13:10 UTC
Parallelism
71/100
Blocked
38%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #88,352,340 · 14 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
1w02w03w14w05w17w29w110w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0xf565ea1f…4245
0x34b655…2a6f
4 touches
1 conflict
0x62b86e44…980e
0x851145…3f07
4 touches
1 conflict
0x00000000…0002
0x48cba2…b48b
4 touches
1 conflict
0x615b0bb8…2589
0x851145…3f07
4 touches
1 conflict
0x6257ccf1…465f
0x851145…3f07
4 touches
1 conflict
0x33a9f4e4…65b5
0x851145…3f07
3 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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity