← previous blocknext block →recent activity

Analyzing

Block #86,226,014

21 transactions · 17 stateful · 2026-07-07 16:13:22 UTC

Parallelism

71/100

Blocked

47%

Avg conflicts / tx

0.86

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #86,226,014  ·  21 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

12 touches
15 conflicts

0x1b5d2e60…99b5

0x34b655…2a6f

6 touches
3 conflicts

0x8d0e98f3…7ba0

0x34b655…2a6f

6 touches
3 conflicts

0x7d42dc8b…fdb6

0x2a68ba…90c5

4 touches
1 conflict

0x28ceceef…ecc2

0x34b655…2a6f

4 touches
1 conflict

0x4461bdda…8980

0x34b655…2a6f

4 touches
1 conflict

0x74e94e75…4913

0x34b655…2a6f

4 touches
1 conflict

0x87886a03…b768

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

15 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity