← previous blocknext block →recent activity

Analyzing

Block #87,355,588

17 transactions · 17 stateful · 2026-07-12 22:05:06 UTC

Parallelism

65/100

Blocked

47%

Avg conflicts / tx

0.82

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #87,355,588  ·  17 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

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x321eac33…6aca

0x34b655…2a6f

4 touches
1 conflict

0x417dbefd…8b60

0x34b655…2a6f

4 touches
1 conflict

0x427f51fd…bd80

0x34b655…2a6f

4 touches
1 conflict

0x636fd21a…9978

0x34b655…2a6f

4 touches
1 conflict

0x72c8aeb2…9921

0x34b655…2a6f

4 touches
1 conflict

0x7e17e82a…9748

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity