← previous blocknext block →recent activity
Analyzing
Block #87,498,758
16 transactions · 14 stateful · 2026-07-13 14:02:34 UTC
Parallelism
75/100
Blocked
50%
Avg conflicts / tx
0.88
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,498,758 · 16 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
1w02w13w04w05w16w27w38w312w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x8a35acfb…d1a9
0x158622…375e
8 touches
6 conflicts
0x8dfb88f5…5592
0x34b655…2a6f
6 touches
3 conflicts
0x6286219a…0721
0x158622…375e
4 touches
1 conflict
0x6a248bdc…3c1b
0x158622…375e
4 touches
1 conflict
0x8a35acfb…d19e
0x158622…375e
4 touches
1 conflict
0x8a35acfb…d1a7
0x158622…375e
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
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