← previous blocknext block →recent activity

Analyzing

Block #86,491,125

15 transactions · 13 stateful · 2026-07-08 21:44:34 UTC

Parallelism

73/100

Blocked

31%

Avg conflicts / tx

0.33

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,491,125  ·  15 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

0xd92a03c7…bfc7

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xfaef08b1…0696

0x34b655…2a6f

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x080ec687…da80

0x34b655…2a6f

4 touches
1 conflict

0x5e2ea201…12de

0x34b655…2a6f

4 touches
1 conflict

0x4f746461…5b03

0x34b655…2a6f

4 touches
1 conflict

0x57592e2a…53b9

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

1 conflict on slot 0xd92a03c739…17bfc7

← previous block·next block →recent activity