← previous blocknext block →recent activity

Analyzing

Block #85,224,114

20 transactions · 15 stateful · 2026-07-03 00:55:02 UTC

Parallelism

85/100

Blocked

53%

Avg conflicts / tx

0.6

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #85,224,114  ·  20 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xea2644f5…8c97

0x34b655…2a6f

6 touches
3 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

6 touches
3 conflicts

0x61553875…1151

0xd32edf…ff58

5 touches
3 conflicts

0x00000000…001b

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002b

0x1b6862…e19c

4 touches
1 conflict

0xd25997d0…a686

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x83f3d320…fb59

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 0xea2644f55c…128c97

← previous block·next block →recent activity