← previous blocknext block →recent activity

Analyzing

Block #90,887,346

17 transactions · 15 stateful · 2026-07-27 22:10:18 UTC

Parallelism

76/100

Blocked

20%

Avg conflicts / tx

0.24

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #90,887,346  ·  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

0xf18906a6…d2e3

0x34b655…2a6f

6 touches
3 conflicts

0xf4e9156d…3c7d

0x34b655…2a6f

4 touches
1 conflict

0xfe2577ac…677b

0x34b655…2a6f

4 touches
1 conflict

0x0b87c899…c0f9

0x34b655…2a6f

4 touches
1 conflict

0x0d67b66f…c9b1

0x34b655…2a6f

4 touches
1 conflict

0x107b89e4…470d

0x34b655…2a6f

4 touches
1 conflict

0x248da771…d0c0

0x34b655…2a6f

4 touches
1 conflict

0x3732c6c9…ded6

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 0xf18906a60b…97d2e3

← previous block·next block →recent activity