← previous blocknext block →recent activity
Analyzing
Block #87,616,986
22 transactions · 20 stateful · 2026-07-14 03:14:05 UTC
Parallelism
68/100
Blocked
45%
Avg conflicts / tx
0.64
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,616,986 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w06w17w28w39w414w015w516w617w018w120w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0xc5490a87…0df8
0x34b655…2a6f
6 touches
3 conflicts
0x4b628349…f327
0x34b655…2a6f
4 touches
1 conflict
0x60dc7b78…d1d5
0x34b655…2a6f
4 touches
1 conflict
0x81ca8c9e…28cb
0x34b655…2a6f
4 touches
1 conflict
0x90d5df31…abd3
0x34b655…2a6f
4 touches
1 conflict
0x92c17fb5…c032
0x34b655…2a6f
4 touches
1 conflict
0xa289c2bf…f5ce
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