← previous blocknext block →recent activity
Analyzing
Block #87,625,792
18 transactions · 18 stateful · 2026-07-14 04:12:57 UTC
Parallelism
67/100
Blocked
44%
Avg conflicts / tx
0.83
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,625,792 · 18 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
3w04w15w26w07w19w010w012w113w115w316w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac61d3a4…7da8
0x34b655…2a6f
8 touches
6 conflicts
0x1175233a…64e7
0x34b655…2a6f
6 touches
3 conflicts
0x18e900fa…07f4
0x34b655…2a6f
6 touches
3 conflicts
0x25329a48…4e00
0x34b655…2a6f
6 touches
3 conflicts
0x4c188934…158e
0x34b655…2a6f
6 touches
3 conflicts
0x56139d82…caaa
0x34b655…2a6f
6 touches
3 conflicts
0x68b75835…d6f3
0x34b655…2a6f
6 touches
3 conflicts
0x6b3ab8d1…ab51
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 0xac61d3a497…e97da8
Audit this contract →
← previous block·next block →recent activity