← previous blocknext block →recent activity

Analyzing

Block #85,158,240

19 transactions · 17 stateful · 2026-07-02 17:36:26 UTC

Parallelism

74/100

Blocked

41%

Avg conflicts / tx

0.68

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #85,158,240  ·  19 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

0x00000000…0002

0x04fdea…47d7

10 touches
10 conflicts

0x2b54cadb…4425

0xd18b7e…414b

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x922c7ebd…6600

0xc8689a…ee79

4 touches
1 conflict

0x13a54fa2…5ae3

0x2a68ba…90c5

4 touches
1 conflict

0x06aed19e…ca57

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x2549dda6…9e24

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: 0x04fdeac2…f747d7

10 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity