← previous blocknext block →recent activity

Analyzing

Block #87,913,845

18 transactions · 17 stateful · 2026-07-15 12:19:43 UTC

Parallelism

83/100

Blocked

41%

Avg conflicts / tx

0.5

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #87,913,845  ·  18 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

0xa013ecc1…7c8f

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0xf3d10975…0d07

0x34b655…2a6f

6 touches
3 conflicts

0x14997ca0…3e65

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4ab

0x34b655…2a6f

4 touches
1 conflict

0x91ace65b…97af

0x34b655…2a6f

4 touches
1 conflict

0xa36930cd…7774

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 0xa013ecc17b…017c8f

← previous block·next block →recent activity