← previous blocknext block →recent activity

Analyzing

Block #85,345,237

20 transactions · 16 stateful · 2026-07-03 14:21:54 UTC

Parallelism

85/100

Blocked

31%

Avg conflicts / tx

0.3

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #85,345,237  ·  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

0x88601476…e1c3

0xfa32f9…f3f0

4 touches
1 conflict

0xb3fb9fb5…64db

0x34b655…2a6f

4 touches
1 conflict

0xb3fb9fb5…64dc

0x34b655…2a6f

4 touches
1 conflict

0xc68d6f14…bdde

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

0x99f666e3…b2a2

0x3bd359…433a

4 touches
1 conflict

0x9194f4a3…10b8

0x754704…b603

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: 0xfa32f9ec…fef3f0

1 conflict on slot 0x88601476d1…cfe1c3

← previous block·next block →recent activity