← previous blocknext block →recent activity

Analyzing

Block #87,361,872

20 transactions · 20 stateful · 2026-07-12 22:47:07 UTC

Parallelism

80/100

Blocked

40%

Avg conflicts / tx

0.55

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #87,361,872  ·  20 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

0x95c47f03…f1bb

0x34b655…2a6f

6 touches
3 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

6 touches
3 conflicts

0x05e83dc2…b7a0

0x34b655…2a6f

4 touches
1 conflict

0x08d66073…e706

0x34b655…2a6f

4 touches
1 conflict

0x21ed3831…61e5

0x34b655…2a6f

4 touches
1 conflict

0x2a3bacb8…164b

0x34b655…2a6f

4 touches
1 conflict

0x2ff1161e…9504

0x34b655…2a6f

4 touches
1 conflict

0x3c4b8fbd…9354

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 0x95c47f0322…51f1bb

← previous block·next block →recent activity