← previous blocknext block →recent activity
Analyzing
Block #87,718,337
11 transactions · 10 stateful · 2026-07-14 14:31:58 UTC
Parallelism
64/100
Blocked
40%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,718,337 · 11 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
1w03w14w27w110w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x521f03f8…dc0e
0x34b655…2a6f
6 touches
3 conflicts
0x52bca665…2468
0x34b655…2a6f
4 touches
1 conflict
0x2e64e234…5cfa
0x34b655…2a6f
4 touches
1 conflict
0x7cb1d883…dc23
0x34b655…2a6f
4 touches
1 conflict
0x8b818135…eff8
0x34b655…2a6f
4 touches
1 conflict
0x8da4cc39…7e25
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x2a686c7e…1481
0x34b655…2a6f
2 touches
0 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
3 conflicts on slot 0x521f03f844…eedc0e
Audit this contract →
← previous block·next block →recent activity