← previous blocknext block →recent activity

Analyzing

Block #85,126,763

20 transactions · 17 stateful · 2026-07-02 14:06:31 UTC

Parallelism

75/100

Blocked

47%

Avg conflicts / tx

0.55

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #85,126,763  ·  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

0x00000000…0002

0x04fdea…47d7

6 touches
3 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

6 touches
3 conflicts

0xfaef08b1…0696

0x34b655…2a6f

6 touches
3 conflicts

0x63da0619…7a55

0x34b655…2a6f

4 touches
1 conflict

0x81df88ae…0e9f

0x34b655…2a6f

4 touches
1 conflict

0x8d773511…5fd3

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x030a8125…dedd

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

3 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity