← previous blocknext block →recent activity

Analyzing

Block #86,845,126

20 transactions · 17 stateful · 2026-07-10 13:12:28 UTC

Parallelism

75/100

Blocked

47%

Avg conflicts / tx

0.65

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #86,845,126  ·  20 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

0x3d158563…8713

0x34b655…2a6f

8 touches
6 conflicts

0xec7fe04a…3c56

0x34b655…2a6f

6 touches
3 conflicts

0x140eb1ca…bc07

0x34b655…2a6f

4 touches
1 conflict

0x25191452…d2ed

0x34b655…2a6f

4 touches
1 conflict

0x4e3abeff…18eb

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

0x34b655…2a6f

4 touches
1 conflict

0x92385428…6941

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 0x3d1585630c…178713

← previous block·next block →recent activity