← previous blocknext block →recent activity

Analyzing

Block #87,354,778

19 transactions · 15 stateful · 2026-07-12 21:59:40 UTC

Parallelism

58/100

Blocked

67%

Avg conflicts / tx

1.21

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #87,354,778  ·  19 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xfaef08b1…0696

0x34b655…2a6f

12 touches
15 conflicts

0xc04561b7…97bb

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x098db796…75a4

0x34b655…2a6f

4 touches
1 conflict

0x1fa0a23d…12b6

0x34b655…2a6f

4 touches
1 conflict

0x25e3730b…24a9

0x34b655…2a6f

4 touches
1 conflict

0x30153288…6d46

0x34b655…2a6f

4 touches
1 conflict

0x51087f5a…61f7

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

15 conflicts on slot 0xfaef08b108…f90696

← previous block·next block →recent activity