← previous blocknext block →recent activity

Analyzing

Block #87,347,632

16 transactions · 15 stateful · 2026-07-12 21:11:54 UTC

Parallelism

69/100

Blocked

53%

Avg conflicts / tx

0.69

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #87,347,632  ·  16 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

0xb7dbe79a…4499

0x34b655…2a6f

6 touches
3 conflicts

0x61377ba1…0bef

0xa6afd3…d132

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x66d892b4…178f

0x34b655…2a6f

4 touches
1 conflict

0x787e6b5e…3130

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

0x34b655…2a6f

4 touches
1 conflict

0x823a3658…acf6

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 0xb7dbe79abd…fd4499

← previous block·next block →recent activity