← previous blocknext block →recent activity

Analyzing

Block #87,688,336

19 transactions · 19 stateful · 2026-07-14 11:10:55 UTC

Parallelism

68/100

Blocked

42%

Avg conflicts / tx

0.84

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #87,688,336  ·  19 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

0xea02471d…1542

0x34b655…2a6f

8 touches
6 conflicts

0xf3d10975…0d07

0x34b655…2a6f

8 touches
6 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0xfe4e62b8…9ade

0x34b655…2a6f

6 touches
3 conflicts

0x4e1ce17e…98a7

0x34b655…2a6f

6 touches
3 conflicts

0x63ad92a0…7912

0x34b655…2a6f

4 touches
1 conflict

0x86aa6553…7dcb

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 0xea02471df2…601542

← previous block·next block →recent activity