← previous blocknext block →recent activity
Analyzing
Block #87,442,716
13 transactions · 10 stateful · 2026-07-13 07:47:46 UTC
Parallelism
69/100
Blocked
30%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,442,716 · 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
2w03w14w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x64c6190b…498c
0x34b655…2a6f
6 touches
3 conflicts
0x95c47f03…f1bb
0x34b655…2a6f
6 touches
3 conflicts
0x4cf5e9f3…cc33
0x34b655…2a6f
4 touches
1 conflict
0x6b259aa9…cfba
0x34b655…2a6f
4 touches
1 conflict
0x6c381064…bc43
0x34b655…2a6f
4 touches
1 conflict
0xdbd174e4…b6f8
0x34b655…2a6f
4 touches
1 conflict
0x032b49e6…03f0
0x34b655…2a6f
4 touches
1 conflict
0x0375bdf9…2806
0x34b655…2a6f
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
3 conflicts on slot 0x64c6190bee…97498c
Audit this contract →
← previous block·next block →recent activity