← previous blocknext block →recent activity

Analyzing

Block #84,501,107

20 transactions · 18 stateful · 2026-06-29 16:33:05 UTC

Parallelism

85/100

Blocked

33%

Avg conflicts / tx

0.4

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #84,501,107  ·  20 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

6 touches
3 conflicts

0xffc2f21e…b393

0x34b655…2a6f

6 touches
3 conflicts

0x8a7af3fd…72a7

0x34b655…2a6f

4 touches
1 conflict

0x8e739938…e7ab

0x34b655…2a6f

4 touches
1 conflict

0x9009e484…2a9b

0x34b655…2a6f

4 touches
1 conflict

0xa0cba198…ea49

0x34b655…2a6f

4 touches
1 conflict

0xab86573c…682e

0x34b655…2a6f

4 touches
1 conflict

0xac206e47…ef7d

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity