← previous blocknext block →recent activity

Analyzing

Block #87,682,747

19 transactions · 18 stateful · 2026-07-14 10:33:33 UTC

Parallelism

74/100

Blocked

39%

Avg conflicts / tx

0.74

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #87,682,747  ·  19 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

8 touches
6 conflicts

0x00893bb8…77ee

0x34b655…2a6f

6 touches
3 conflicts

0xa10e928f…3b92

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x2877f440…c2c8

0x34b655…2a6f

4 touches
1 conflict

0x2df6f59b…d662

0x34b655…2a6f

4 touches
1 conflict

0x5a135c5e…c138

0x34b655…2a6f

4 touches
1 conflict

0x68a3bb97…53c2

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 0x59dccbd857…c52bf6

← previous block·next block →recent activity