← previous blocknext block →recent activity
Analyzing
Block #87,663,017
39 transactions · 30 stateful · 2026-07-14 08:21:43 UTC
Parallelism
87/100
Blocked
37%
Avg conflicts / tx
0.56
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,663,017 · 39 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w06w07w19w011w012w114w220w024w025w126w227w228w329w030w131w432w033w136w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0xc948dbdc…199a
0x34b655…2a6f
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x65e795ca…0320
0x34b655…2a6f
6 touches
3 conflicts
0x95fc4780…3ce6
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0004
0x5afd3e…7620
4 touches
1 conflict
0x00000000…0005
0x5afd3e…7620
4 touches
1 conflict
0x1bc72735…8ce0
0x5afd3e…7620
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