← previous blocknext block →recent activity
Analyzing
Block #87,593,997
14 transactions · 12 stateful · 2026-07-14 00:40:20 UTC
Parallelism
57/100
Blocked
58%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,593,997 · 14 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w38w49w512w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2b5101ac…090b
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x176771f9…c1a4
0x34b655…2a6f
4 touches
1 conflict
0x2a5bc5cd…0a17
0x34b655…2a6f
4 touches
1 conflict
0x2a88784d…f1be
0x34b655…2a6f
4 touches
1 conflict
0x2df6f59b…d662
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
6 conflicts on slot 0x2b5101acd1…7c090b
Audit this contract →
← previous block·next block →recent activity