← previous blocknext block →recent activity

Analyzing

Block #87,588,092

14 transactions · 11 stateful · 2026-07-14 00:00:50 UTC

Parallelism

71/100

Blocked

45%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #87,588,092  ·  14 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

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x4467ecee…e95b

0x34b655…2a6f

6 touches
3 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x1f2cd70b…94be

0x34b655…2a6f

4 touches
1 conflict

0x226c44fc…d8ef

0x34b655…2a6f

4 touches
1 conflict

0x27bfe98b…2053

0x34b655…2a6f

4 touches
1 conflict

0x344bc09a…942f

0x34b655…2a6f

4 touches
1 conflict

0x366c7d57…0ed1

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

3 conflicts on slot 0x4467eceedf…bfe95b

← previous block·next block →recent activity