← previous blocknext block →recent activity

Analyzing

Block #87,793,882

19 transactions · 18 stateful · 2026-07-14 22:57:19 UTC

Parallelism

63/100

Blocked

44%

Avg conflicts / tx

0.74

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #87,793,882  ·  19 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

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0x9465204c…bf37

0x34b655…2a6f

6 touches
3 conflicts

0x25ff7717…d4af

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x67905f6e…02a1

0x34b655…2a6f

4 touches
1 conflict

0x9ae859db…2d84

0x34b655…2a6f

4 touches
1 conflict

0x9e2213fb…dee5

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

6 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity