← previous blocknext block →recent activity

Analyzing

Block #87,727,100

21 transactions · 21 stateful · 2026-07-14 15:30:36 UTC

Parallelism

71/100

Blocked

38%

Avg conflicts / tx

0.95

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #87,727,100  ·  21 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x424934c8…f2f1

0x34b655…2a6f

6 touches
3 conflicts

0x64aaadbf…f9f3

0x34b655…2a6f

6 touches
3 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0xc4de6652…13f4

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x44a2c3ff…0abc

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x58620f29…db5a

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 0x424934c865…4af2f1

← previous block·next block →recent activity