← previous blocknext block →recent activity
Analyzing
Block #87,623,804
20 transactions · 18 stateful · 2026-07-14 03:59:39 UTC
Parallelism
70/100
Blocked
28%
Avg conflicts / tx
0.8
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,623,804 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w28w39w410w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x99c46e97…c1b2
0x34b655…2a6f
12 touches
15 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0xc36fa358…24cb
0x34b655…2a6f
10 touches
10 conflicts
0xb176789b…c34b
0x34b655…2a6f
8 touches
6 conflicts
0x8b87ece6…3353
0x34b655…2a6f
6 touches
3 conflicts
0xaedc3dd6…3c3b
0x34b655…2a6f
6 touches
3 conflicts
0x81ca8c9e…28cb
0x34b655…2a6f
4 touches
1 conflict
0x9692085a…b7be
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
15 conflicts on slot 0x99c46e97a0…cac1b2
Audit this contract →
← previous block·next block →recent activity