← previous blocknext block →recent activity
Analyzing
Block #87,712,186
27 transactions · 21 stateful · 2026-07-14 13:50:39 UTC
Parallelism
85/100
Blocked
43%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,712,186 · 27 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w110w111w212w314w115w016w117w018w020w021w122w125w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb65644e3…33ce
0x34b655…2a6f
8 touches
6 conflicts
0xc0b9bd73…7f1c
0x34b655…2a6f
8 touches
6 conflicts
0x5170a218…3a84
0xc8689a…ee79
6 touches
3 conflicts
0x4b26a3bf…bc4f
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x74fd0a9b…3aaa
0x34b655…2a6f
6 touches
3 conflicts
0xd9072021…db76
0x34b655…2a6f
6 touches
3 conflicts
0xdfbd8991…5bd1
0x34b655…2a6f
6 touches
3 conflicts
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
6 conflicts on slot 0xb65644e3fe…5033ce
Audit this contract →
← previous block·next block →recent activity