← previous blocknext block →recent activity

Analyzing

Block #86,925,073

22 transactions · 20 stateful · 2026-07-10 22:07:01 UTC

Parallelism

77/100

Blocked

40%

Avg conflicts / tx

0.5

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #86,925,073  ·  22 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

0xa08f40b2…9a93

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x1509d2c8…8461

0x34b655…2a6f

4 touches
1 conflict

0x17c3727d…cb0e

0x34b655…2a6f

4 touches
1 conflict

0x3a996b35…bc8f

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x4b3b0587…0912

0x34b655…2a6f

4 touches
1 conflict

0xbda6c72f…2a3c

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

3 conflicts on slot 0xa08f40b255…099a93

← previous block·next block →recent activity