← previous blocknext block →recent activity

Analyzing

Block #87,642,314

21 transactions · 14 stateful · 2026-07-14 06:03:23 UTC

Parallelism

86/100

Blocked

14%

Avg conflicts / tx

0.14

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #87,642,314  ·  21 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x53f393fa…00b9

0x34b655…2a6f

6 touches
3 conflicts

0xbf6de35e…bafd

0x34b655…2a6f

6 touches
3 conflicts

0xd82d1c5a…0850

0x34b655…2a6f

6 touches
3 conflicts

0x0733be30…112f

0x34b655…2a6f

4 touches
1 conflict

0x8b501dcf…1040

0x34b655…2a6f

4 touches
1 conflict

0x92aaa948…2b73

0x34b655…2a6f

4 touches
1 conflict

0x7b6c252d…a696

0x34b655…2a6f

4 touches
1 conflict

0x387231f6…6b29

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 0x53f393fafd…2a00b9

← previous block·next block →recent activity