← previous blocknext block →recent activity
Analyzing
Block #87,592,053
13 transactions · 12 stateful · 2026-07-14 00:27:20 UTC
Parallelism
77/100
Blocked
33%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,592,053 · 13 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
1w03w04w16w210w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0eeb2a30…6909
0x34b655…2a6f
6 touches
3 conflicts
0x0ea46b1d…c9a4
0x34b655…2a6f
4 touches
1 conflict
0x15c9b5bf…f732
0x34b655…2a6f
4 touches
1 conflict
0x290bd5b0…850c
0x34b655…2a6f
4 touches
1 conflict
0x2cfbdce8…37ca
0x34b655…2a6f
4 touches
1 conflict
0x3cb8c8c3…22f4
0x34b655…2a6f
4 touches
1 conflict
0x44a7d98d…ac09
0x34b655…2a6f
4 touches
1 conflict
0x463c743e…0135
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 0x0eeb2a3089…8a6909
Audit this contract →
← previous block·next block →recent activity