← previous blocknext block →recent activity

Analyzing

Block #86,135,073

19 transactions · 18 stateful · 2026-07-07 06:06:13 UTC

Parallelism

89/100

Blocked

28%

Avg conflicts / tx

0.26

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #86,135,073  ·  19 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

0x38b5b2ce…c5bb

0xfa32f9…f3f0

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x7b2f3e6d…978f

0x34b655…2a6f

4 touches
1 conflict

0x89999c15…fdac

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

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 0x38b5b2ceac…4cc5bb

← previous block·next block →recent activity