← previous blocknext block →recent activity

Analyzing

Block #87,328,951

20 transactions · 18 stateful · 2026-07-12 19:07:00 UTC

Parallelism

75/100

Blocked

44%

Avg conflicts / tx

0.6

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #87,328,951  ·  20 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xb6ed530c…d450

0x34b655…2a6f

8 touches
6 conflicts

0x21d22421…0b7a

0x34b655…2a6f

4 touches
1 conflict

0x31d2c775…b3b9

0x34b655…2a6f

4 touches
1 conflict

0x3347cbe5…846c

0x34b655…2a6f

4 touches
1 conflict

0x451f5977…7300

0x34b655…2a6f

4 touches
1 conflict

0x67db761a…4fa1

0x34b655…2a6f

4 touches
1 conflict

0x85a88798…f85e

0x34b655…2a6f

4 touches
1 conflict

0x8631c06c…1922

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 0xb6ed530c56…eed450

← previous block·next block →recent activity