← previous blocknext block →recent activity

Analyzing

Block #86,214,782

19 transactions · 18 stateful · 2026-07-07 14:58:22 UTC

Parallelism

53/100

Blocked

50%

Avg conflicts / tx

2

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #86,214,782  ·  19 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

18 touches
36 conflicts

0x0db8e93a…7dd1

0x34b655…2a6f

4 touches
1 conflict

0x10797f0b…439a

0x34b655…2a6f

4 touches
1 conflict

0x2697123c…8526

0x34b655…2a6f

4 touches
1 conflict

0x3280f198…a541

0x34b655…2a6f

4 touches
1 conflict

0x3a7fb5b5…f0e5

0x34b655…2a6f

4 touches
1 conflict

0x41be9e75…9773

0x34b655…2a6f

4 touches
1 conflict

0x4bfe0363…4bfa

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

36 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity