← previous blocknext block →recent activity

Analyzing

Block #87,291,923

19 transactions · 18 stateful · 2026-07-12 14:59:26 UTC

Parallelism

74/100

Blocked

44%

Avg conflicts / tx

0.84

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #87,291,923  ·  19 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

0xd99b3b64…1c95

0x34b655…2a6f

8 touches
6 conflicts

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0xbc94dfe1…0b3d

0x34b655…2a6f

6 touches
3 conflicts

0xedcf2991…8551

0x34b655…2a6f

6 touches
3 conflicts

0x70b87e4d…65d5

0x34b655…2a6f

6 touches
3 conflicts

0xfaef08b1…0696

0x34b655…2a6f

6 touches
3 conflicts

0x7506443a…4820

0x34b655…2a6f

4 touches
1 conflict

0x7523ad90…2ba5

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 0xd99b3b6441…7a1c95

← previous block·next block →recent activity