← previous blocknext block →recent activity
Analyzing
Block #87,748,482
23 transactions · 21 stateful · 2026-07-14 17:53:37 UTC
Parallelism
83/100
Blocked
52%
Avg conflicts / tx
0.96
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,748,482 · 23 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
5w06w17w28w39w010w112w113w214w016w317w118w219w122w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x3a5446d7…e4fc
0x34b655…2a6f
6 touches
3 conflicts
0x579ab5da…e8d7
0x34b655…2a6f
6 touches
3 conflicts
0x644919d7…9727
0x34b655…2a6f
6 touches
3 conflicts
0x70d66bd9…0ffa
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0xe1fe8278…8591
0x34b655…2a6f
6 touches
3 conflicts
0xe732567d…b65d
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