← previous blocknext block →recent activity

Analyzing

Block #86,812,056

20 transactions · 18 stateful · 2026-07-10 09:31:14 UTC

Parallelism

65/100

Blocked

44%

Avg conflicts / tx

0.9

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #86,812,056  ·  20 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x42e08579…09bb

0x34b655…2a6f

8 touches
6 conflicts

0xb5a3b1be…8122

0x34b655…2a6f

8 touches
6 conflicts

0xf4d0bddb…07a4

0x34b655…2a6f

6 touches
3 conflicts

0x3684bb9c…2e61

0x34b655…2a6f

6 touches
3 conflicts

0x8d888c90…5479

0x34b655…2a6f

4 touches
1 conflict

0xfaef08b1…0696

0x34b655…2a6f

4 touches
1 conflict

0x13a54fa2…5ae3

0x2a68ba…90c5

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