← previous blocknext block →recent activity

Analyzing

Block #87,783,598

20 transactions · 18 stateful · 2026-07-14 21:48:32 UTC

Parallelism

65/100

Blocked

44%

Avg conflicts / tx

0.7

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #87,783,598  ·  20 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xf3d10975…0d07

0x34b655…2a6f

6 touches
3 conflicts

0xf5ea108a…dbf6

0x34b655…2a6f

6 touches
3 conflicts

0x737acb78…fce8

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x310afe2c…83e1

0x34b655…2a6f

6 touches
3 conflicts

0x7c51d9aa…af39

0x34b655…2a6f

4 touches
1 conflict

0x898d9b8a…d1ef

0x34b655…2a6f

4 touches
1 conflict

0x8bf661cb…bcd2

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 0xf3d10975b0…050d07

← previous block·next block →recent activity