← previous blocknext block →recent activity
Analyzing
Block #87,625,981
25 transactions · 22 stateful · 2026-07-14 04:14:13 UTC
Parallelism
80/100
Blocked
41%
Avg conflicts / tx
0.88
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,625,981 · 25 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
1w02w15w06w17w28w09w310w411w012w113w117w223w024w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x08330b36…ae29
0x34b655…2a6f
8 touches
6 conflicts
0x2d94ecd9…43db
0x34b655…2a6f
6 touches
3 conflicts
0x49f75237…44f4
0x34b655…2a6f
6 touches
3 conflicts
0x53bddbe8…2e5e
0x34b655…2a6f
6 touches
3 conflicts
0x5b145de0…367c
0xc8689a…ee79
6 touches
3 conflicts
0x1175233a…64e7
0x34b655…2a6f
6 touches
3 conflicts
0xd19c9d38…b459
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
10 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity