← previous blocknext block →recent activity

Analyzing

Block #87,736,151

20 transactions · 19 stateful · 2026-07-14 16:31:07 UTC

Parallelism

55/100

Blocked

47%

Avg conflicts / tx

1.2

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #87,736,151  ·  20 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

12 touches
15 conflicts

0x006c3b86…59a9

0x34b655…2a6f

6 touches
3 conflicts

0x307414a5…7214

0x34b655…2a6f

6 touches
3 conflicts

0x548145a9…cfce

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x7fa1794c…3323

0x34b655…2a6f

6 touches
3 conflicts

0xdfbd8991…5bd1

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity