← previous blocknext block →recent activity

Analyzing

Block #87,753,174

24 transactions · 23 stateful · 2026-07-14 18:25:00 UTC

Parallelism

83/100

Blocked

30%

Avg conflicts / tx

0.58

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #87,753,174  ·  24 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

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0x0733be30…112f

0x34b655…2a6f

6 touches
3 conflicts

0x33da0dfa…bac6

0x34b655…2a6f

4 touches
1 conflict

0x378c030c…a8a4

0x34b655…2a6f

4 touches
1 conflict

0x378c030c…a8a5

0x34b655…2a6f

4 touches
1 conflict

0x40883ce5…2ae2

0x34b655…2a6f

4 touches
1 conflict

0x41ebf7ed…f662

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 0x7e5ea60ab2…b0c4aa

← previous block·next block →recent activity