← previous blocknext block →recent activity

Analyzing

Block #87,749,525

19 transactions · 17 stateful · 2026-07-14 18:00:36 UTC

Parallelism

68/100

Blocked

47%

Avg conflicts / tx

0.74

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #87,749,525  ·  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

0x7e5ea60a…c4aa

0x34b655…2a6f

10 touches
10 conflicts

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0x55c2c22c…0474

0x34b655…2a6f

6 touches
3 conflicts

0x595cbd16…dac4

0x34b655…2a6f

4 touches
1 conflict

0x6638e124…bc7f

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4ab

0x34b655…2a6f

4 touches
1 conflict

0x807be1c1…8f98

0x34b655…2a6f

4 touches
1 conflict

0xa3d14dff…15d3

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

10 conflicts on slot 0x7e5ea60ab2…b0c4aa

← previous block·next block →recent activity