← previous blocknext block →recent activity

Analyzing

Block #87,871,363

23 transactions · 18 stateful · 2026-07-15 07:35:32 UTC

Parallelism

87/100

Blocked

33%

Avg conflicts / tx

0.39

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #87,871,363  ·  23 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0x0733be30…112f

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x680ca7d7…2df4

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…00c9

0x34b655…2a6f

4 touches
1 conflict

0x0c53719e…0366

0x34b655…2a6f

4 touches
1 conflict

0x313d3d93…4aa2

0x34b655…2a6f

4 touches
1 conflict

0x53ca44ec…625f

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 0x6fe7d366be…a578ff

← previous block·next block →recent activity