← previous blocknext block →recent activity

Analyzing

Block #88,159,144

17 transactions · 17 stateful · 2026-07-16 15:40:39 UTC

Parallelism

76/100

Blocked

47%

Avg conflicts / tx

0.71

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #88,159,144  ·  17 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

0x1e56f6b6…5940

0x34b655…2a6f

6 touches
3 conflicts

0x2b5ab9a3…58c5

0x34b655…2a6f

4 touches
1 conflict

0x310afe2c…83e1

0x34b655…2a6f

4 touches
1 conflict

0x3de501bc…51f1

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x52a2ba74…f2f6

0x34b655…2a6f

4 touches
1 conflict

0x69a45f39…39aa

0x34b655…2a6f

4 touches
1 conflict

0x6a46e23f…d28d

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 0x1e56f6b6e1…615940

← previous block·next block →recent activity