← previous blocknext block →recent activity
Analyzing
Block #87,456,346
22 transactions · 19 stateful · 2026-07-13 09:18:58 UTC
Parallelism
86/100
Blocked
16%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,456,346 · 22 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w07w110w011w115w016w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x0505d078…ea97
0x34b655…2a6f
4 touches
1 conflict
0x18e900fa…07f4
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x37a59111…090b
0x34b655…2a6f
4 touches
1 conflict
0x48a2b821…513e
0x34b655…2a6f
4 touches
1 conflict
0x4d96211a…5c06
0x34b655…2a6f
4 touches
1 conflict
0x5db87b77…13f5
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 0x737acb7813…fafce8
Audit this contract →
← previous block·next block →recent activity