← previous blocknext block →recent activity

Analyzing

Block #86,307,733

21 transactions · 17 stateful · 2026-07-08 01:19:00 UTC

Parallelism

81/100

Blocked

35%

Avg conflicts / tx

0.33

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,307,733  ·  21 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

6 touches
3 conflicts

0xa343fc52…5575

0x851145…3f07

4 touches
1 conflict

0xa224e433…7cf2

0x065c9d…c394

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x4fe95978…4ea7

0x34b655…2a6f

4 touches
1 conflict

0x533efc9c…80d4

0x34b655…2a6f

4 touches
1 conflict

0xec0e0220…cb90

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x851145…3f07

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

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity