← previous blocknext block →recent activity
Analyzing
Block #87,524,770
14 transactions · 13 stateful · 2026-07-13 16:57:11 UTC
Parallelism
79/100
Blocked
31%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,524,770 · 14 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
2w03w04w16w19w211w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc3688185…9b36
0x34b655…2a6f
4 touches
1 conflict
0xda03a1b2…8632
0x34b655…2a6f
4 touches
1 conflict
0xdb3ef610…e653
0x34b655…2a6f
4 touches
1 conflict
0xfdd655b8…bf89
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x1ebb35bb…ef2a
0x34b655…2a6f
4 touches
1 conflict
0x1f0fb2d1…7abb
0x34b655…2a6f
4 touches
1 conflict
0x59991669…58c6
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
1 conflict on slot 0xc36881859a…c49b36
Audit this contract →
← previous block·next block →recent activity