← previous blocknext block →recent activity

Analyzing

Block #87,712,049

21 transactions · 17 stateful · 2026-07-14 13:49:44 UTC

Parallelism

76/100

Blocked

41%

Avg conflicts / tx

0.52

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #87,712,049  ·  21 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

0xfc4d32c0…39f9

0x34b655…2a6f

6 touches
3 conflicts

0x6323c5ea…ce8a

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0xbf78ee7f…e7fd

0x34b655…2a6f

6 touches
3 conflicts

0x78694995…f66c

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x3095aa84…e9e3

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 0xfc4d32c0b5…3239f9

← previous block·next block →recent activity