← previous blocknext block →recent activity

Analyzing

Block #86,395,214

20 transactions · 19 stateful · 2026-07-08 11:03:30 UTC

Parallelism

60/100

Blocked

47%

Avg conflicts / tx

1

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #86,395,214  ·  20 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

12 touches
15 conflicts

0xefcdf197…96a2

0x34b655…2a6f

6 touches
3 conflicts

0x49cbdb1b…bda4

0x065c9d…c394

4 touches
1 conflict

0x42bb0ac5…6b33

0x34b655…2a6f

4 touches
1 conflict

0x4681609f…6493

0x34b655…2a6f

4 touches
1 conflict

0x47861365…d699

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x89fa7367…f5d4

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

15 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity