← previous blocknext block →recent activity
Analyzing
Block #87,498,920
25 transactions · 23 stateful · 2026-07-13 14:03:39 UTC
Parallelism
64/100
Blocked
52%
Avg conflicts / tx
1.44
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #87,498,920 · 25 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w28w39w410w511w612w223w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8cf1f868…c5af
0x34b655…2a6f
14 touches
21 conflicts
0x5170a218…3a84
0xc8689a…ee79
10 touches
10 conflicts
0x6b2ba712…0214
0x34b655…2a6f
10 touches
10 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x727fbce7…0c80
0x34b655…2a6f
10 touches
10 conflicts
0xad0c7701…1d83
0x34b655…2a6f
10 touches
10 conflicts
0xe1fe8278…8591
0x34b655…2a6f
10 touches
10 conflicts
0xe732567d…b65d
0x34b655…2a6f
10 touches
10 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
21 conflicts on slot 0x8cf1f86890…38c5af
Audit this contract →
← previous block·next block →recent activity