← previous blocknext block →recent activity

Analyzing

Block #86,450,247

22 transactions · 20 stateful · 2026-07-08 17:11:05 UTC

Parallelism

64/100

Blocked

40%

Avg conflicts / tx

0.77

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #86,450,247  ·  22 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xfaef08b1…0696

0x34b655…2a6f

8 touches
6 conflicts

0x3230277c…ef39

0xc8689a…ee79

4 touches
1 conflict

0x13a54fa2…5ae3

0x2a68ba…90c5

4 touches
1 conflict

0x63ee66d8…e145

0x34b655…2a6f

4 touches
1 conflict

0xb5f244d5…f550

0x34b655…2a6f

4 touches
1 conflict

0xb624d2ea…8c87

0x34b655…2a6f

4 touches
1 conflict

0xd92a03c7…bfc7

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