← previous blocknext block →recent activity
Analyzing
Block #87,576,024
38 transactions · 29 stateful · 2026-07-13 22:40:07 UTC
Parallelism
71/100
Blocked
72%
Avg conflicts / tx
2.37
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #87,576,024 · 38 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w06w113w014w115w116w217w318w419w520w621w722w826w327w428w530w631w634w736w937w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
16 touches
28 conflicts
0x8252706a…7ca5
0x34b655…2a6f
14 touches
21 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
14 touches
21 conflicts
0x0733be30…112f
0x34b655…2a6f
12 touches
15 conflicts
0xb2a28991…3db8
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x2d651956…12e8
0x34b655…2a6f
10 touches
10 conflicts
0x5e17e5be…d212
0x34b655…2a6f
8 touches
6 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
28 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity