← previous blocknext block →recent activity
Analyzing
Block #87,717,210
18 transactions · 16 stateful · 2026-07-14 14:24:26 UTC
Parallelism
67/100
Blocked
44%
Avg conflicts / tx
0.72
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,717,210 · 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
4w05w16w07w110w211w313w316w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc9dce17a…a1a1
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x2aa3a932…44f1
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4fc141d9…bb36
0x34b655…2a6f
4 touches
1 conflict
0x5c1b2ba0…c6b6
0x34b655…2a6f
4 touches
1 conflict
0x676f52d1…89e6
0x34b655…2a6f
4 touches
1 conflict
0x6b259aa9…cfba
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 0xc9dce17a10…8ca1a1
Audit this contract →
← previous block·next block →recent activity