← previous blocknext block →recent activity
Analyzing
Block #87,705,813
35 transactions · 27 stateful · 2026-07-14 13:08:01 UTC
Parallelism
86/100
Blocked
41%
Avg conflicts / tx
0.51
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,705,813 · 35 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
2w05w09w111w012w115w016w117w218w320w021w022w123w125w231w232w333w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x5170a218…3a84
0xc8689a…ee79
6 touches
3 conflicts
0x63c900f4…2600
0x34b655…2a6f
6 touches
3 conflicts
0x7520cab2…dc7f
0x34b655…2a6f
6 touches
3 conflicts
0xad0c7701…1d83
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xe1fe8278…8591
0x34b655…2a6f
6 touches
3 conflicts
0xe68de8d4…7a84
0x34b655…2a6f
6 touches
3 conflicts
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