← previous blocknext block →recent activity

Analyzing

Block #87,331,215

17 transactions · 16 stateful · 2026-07-12 19:22:09 UTC

Parallelism

76/100

Blocked

38%

Avg conflicts / tx

0.65

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #87,331,215  ·  17 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xbcbf5d09…8bac

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x2b7950c1…2342

0x34b655…2a6f

6 touches
3 conflicts

0xd8bc53a3…c2fe

0x34b655…2a6f

6 touches
3 conflicts

0x59a54ff4…d21b

0x34b655…2a6f

4 touches
1 conflict

0x67db761a…4fa1

0x34b655…2a6f

4 touches
1 conflict

0x732ce5dc…9452

0x34b655…2a6f

4 touches
1 conflict

0x75eb421e…ccae

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 0xbcbf5d09a8…c68bac

← previous block·next block →recent activity