← previous blocknext block →recent activity

Analyzing

Block #84,605,655

19 transactions · 16 stateful · 2026-06-30 04:10:38 UTC

Parallelism

79/100

Blocked

44%

Avg conflicts / tx

0.53

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #84,605,655  ·  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

0xf28082df…312c

0x34b655…2a6f

6 touches
3 conflicts

0x614241af…8413

0x34b655…2a6f

6 touches
3 conflicts

0x03fb27fd…0c06

0x34b655…2a6f

6 touches
3 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

6 touches
3 conflicts

0x3f75fb9e…0d2e

0x34b655…2a6f

4 touches
1 conflict

0x587911c7…9e01

0x34b655…2a6f

4 touches
1 conflict

0x5f447bf3…57c7

0x34b655…2a6f

4 touches
1 conflict

0x67d8b378…f2f8

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 0xf28082df38…4b312c

← previous block·next block →recent activity