← previous blocknext block →recent activity

Analyzing

Block #87,785,186

20 transactions · 18 stateful · 2026-07-14 21:59:10 UTC

Parallelism

75/100

Blocked

39%

Avg conflicts / tx

0.8

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #87,785,186  ·  20 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x59dccbd8…2bf6

0x34b655…2a6f

10 touches
10 conflicts

0x0733be30…112f

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0xf3d10975…0d07

0x34b655…2a6f

6 touches
3 conflicts

0x13f56f67…c66c

0x34b655…2a6f

4 touches
1 conflict

0x2f14cd2c…b5f4

0x34b655…2a6f

4 touches
1 conflict

0x3a51d8ed…0c97

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

10 conflicts on slot 0x59dccbd857…c52bf6

← previous block·next block →recent activity