← previous blocknext block →recent activity

Analyzing

Block #87,732,356

20 transactions · 18 stateful · 2026-07-14 16:05:44 UTC

Parallelism

80/100

Blocked

44%

Avg conflicts / tx

0.6

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #87,732,356  ·  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

0x5c591136…d322

0x34b655…2a6f

6 touches
3 conflicts

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0xf481b267…dc7d

0x34b655…2a6f

6 touches
3 conflicts

0x286711a5…b3bf

0x34b655…2a6f

4 touches
1 conflict

0x2d7ea048…d78e

0x34b655…2a6f

4 touches
1 conflict

0x307414a5…7214

0x34b655…2a6f

4 touches
1 conflict

0x4b880990…8569

0x34b655…2a6f

4 touches
1 conflict

0x58266ec9…8ef7

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 0x5c591136e9…b7d322

← previous block·next block →recent activity