← previous blocknext block →recent activity
Analyzing
Block #87,585,201
21 transactions · 16 stateful · 2026-07-13 23:41:30 UTC
Parallelism
67/100
Blocked
50%
Avg conflicts / tx
0.86
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,585,201 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w27w311w412w413w014w519w520w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd2453506…54e4
0x34b655…2a6f
10 touches
10 conflicts
0x4467ecee…e95b
0x34b655…2a6f
8 touches
6 conflicts
0x5d2267cd…440e
0x34b655…2a6f
6 touches
3 conflicts
0xc8fec9ca…2d60
0x34b655…2a6f
5 touches
3 conflicts
0x21158693…63e2
0x34b655…2a6f
4 touches
1 conflict
0x2447fab0…811d
0x34b655…2a6f
4 touches
1 conflict
0x25329a48…4e00
0x34b655…2a6f
4 touches
1 conflict
0x30278615…7ac6
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
10 conflicts on slot 0xd2453506e1…f954e4
Audit this contract →
← previous block·next block →recent activity