← previous blocknext block →recent activity

Analyzing

Block #85,360,148

27 transactions · 21 stateful · 2026-07-03 16:01:11 UTC

Parallelism

78/100

Blocked

33%

Avg conflicts / tx

0.63

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #85,360,148  ·  27 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x3e505a15…70f8

0x34b655…2a6f

6 touches
3 conflicts

0xef02ed46…48a4

0x34b655…2a6f

6 touches
3 conflicts

0x5149ba0e…d954

0x754704…b603

4 touches
1 conflict

0x09e0690d…6e3d

0xe52b14…7230

4 touches
1 conflict

0x0b0c2e8d…c1b8

0xe52b14…7230

4 touches
1 conflict

0x35c39ffe…a8d6

0xe52b14…7230

4 touches
1 conflict

0x3cebc8f1…975c

0xe52b14…7230

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