← previous blocknext block →recent activity
Analyzing
Block #87,452,759
18 transactions · 14 stateful · 2026-07-13 08:54:57 UTC
Parallelism
72/100
Blocked
29%
Avg conflicts / tx
0.56
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,452,759 · 18 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
2w03w16w27w38w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc36fa358…24cb
0x34b655…2a6f
10 touches
10 conflicts
0x93b6fab0…09d6
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x375e887b…a362
0x34b655…2a6f
6 touches
3 conflicts
0x709cb1f7…ed38
0x34b655…2a6f
6 touches
3 conflicts
0x30ab53da…3529
0x34b655…2a6f
6 touches
3 conflicts
0x375e887b…a361
0x34b655…2a6f
6 touches
3 conflicts
0x71cd2af8…dbd4
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 0xc36fa35805…6f24cb
Audit this contract →
← previous block·next block →recent activity