← previous blocknext block →recent activity
Analyzing
Block #87,723,825
23 transactions · 21 stateful · 2026-07-14 15:08:40 UTC
Parallelism
78/100
Blocked
38%
Avg conflicts / tx
0.65
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,723,825 · 23 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
3w04w15w06w27w38w411w113w016w117w219w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x5ec64628…72e4
0x34b655…2a6f
8 touches
6 conflicts
0xf4713590…d750
0x34b655…2a6f
8 touches
6 conflicts
0x07fc7174…a4c5
0x34b655…2a6f
6 touches
3 conflicts
0x3b552ea8…3a4b
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xf549aab8…3c09
0x34b655…2a6f
6 touches
3 conflicts
0x5170a218…3a84
0xc8689a…ee79
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