← previous blocknext block →recent activity
Analyzing
Block #87,585,524
13 transactions · 11 stateful · 2026-07-13 23:43:40 UTC
Parallelism
69/100
Blocked
36%
Avg conflicts / tx
0.77
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,585,524 · 13 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
2w04w05w16w27w39w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x26ba619e…edfe
0x34b655…2a6f
8 touches
6 conflicts
0x2e64e234…5cfa
0x34b655…2a6f
8 touches
6 conflicts
0x63c900f4…2600
0x34b655…2a6f
8 touches
6 conflicts
0xde4c010f…59ad
0x34b655…2a6f
8 touches
6 conflicts
0xd2453506…54e4
0x34b655…2a6f
8 touches
6 conflicts
0xa80684c9…3948
0x34b655…2a6f
8 touches
6 conflicts
0x5170a218…3a84
0xc8689a…ee79
8 touches
6 conflicts
0x6fe7d366…78ff
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 0x26ba619e62…1cedfe
Audit this contract →
← previous block·next block →recent activity