← previous blocknext block →recent activity

Analyzing

Block #84,525,113

19 transactions · 19 stateful · 2026-06-29 19:13:11 UTC

Parallelism

79/100

Blocked

37%

Avg conflicts / tx

0.53

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #84,525,113  ·  19 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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x67d8b378…f2f8

0x34b655…2a6f

6 touches
3 conflicts

0xc99e7125…81b1

0x34b655…2a6f

5 touches
3 conflicts

0x213a54fa…c85f

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x5d4a3441…e31c

0x34b655…2a6f

4 touches
1 conflict

0x695d21ae…f4bd

0x34b655…2a6f

4 touches
1 conflict

0x74fd0a9b…3aaa

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