← previous blocknext block →recent activity
Analyzing
Block #87,722,779
14 transactions · 14 stateful · 2026-07-14 15:01:40 UTC
Parallelism
64/100
Blocked
43%
Avg conflicts / tx
0.71
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,722,779 · 14 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
2w03w14w26w38w410w011w113w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0xa3a621f8…75a2
0x34b655…2a6f
6 touches
3 conflicts
0xaf498679…7732
0x34b655…2a6f
6 touches
3 conflicts
0x4cee015b…1a5e
0x34b655…2a6f
4 touches
1 conflict
0x5036f376…c06a
0x34b655…2a6f
4 touches
1 conflict
0x5a7505f7…a94d
0x34b655…2a6f
4 touches
1 conflict
0x7799fd62…0d1c
0x34b655…2a6f
4 touches
1 conflict
0x921a58d1…db22
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