← previous blocknext block →recent activity

Analyzing

Block #85,174,903

16 transactions · 16 stateful · 2026-07-02 19:27:17 UTC

Parallelism

88/100

Blocked

13%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #85,174,903  ·  16 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

4 touches
1 conflict

0xfa1a8731…ca65

0x34b655…2a6f

4 touches
1 conflict

0xffb8950c…23c6

0x34b655…2a6f

4 touches
1 conflict

0x13a54fa2…5ae3

0x2a68ba…90c5

4 touches
1 conflict

0x03fb27fd…0c06

0x34b655…2a6f

4 touches
1 conflict

0xd1a8b9bd…6f8c

0x34b655…2a6f

4 touches
1 conflict

0x2b111712…0e59

0x34b655…2a6f

4 touches
1 conflict

0x465cad5f…fd93

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

1 conflict on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity