← previous blocknext block →recent activity

Analyzing

Block #87,712,143

19 transactions · 17 stateful · 2026-07-14 13:50:22 UTC

Parallelism

79/100

Blocked

41%

Avg conflicts / tx

0.79

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #87,712,143  ·  19 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xf4f4af3b…c5bd

0x34b655…2a6f

8 touches
6 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0x9c7d2e4b…499b

0x34b655…2a6f

6 touches
3 conflicts

0x3be29374…1df9

0x34b655…2a6f

4 touches
1 conflict

0x3d4584df…ffed

0x34b655…2a6f

4 touches
1 conflict

0x42f5c83a…a2d6

0x34b655…2a6f

4 touches
1 conflict

0x5e5ce24b…6023

0x34b655…2a6f

4 touches
1 conflict

0x5ec64628…72e4

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 0xf4f4af3b10…72c5bd

← previous block·next block →recent activity