← previous blocknext block →recent activity

Analyzing

Block #83,904,084

17 transactions · 15 stateful · 2026-06-26 22:15:08 UTC

Parallelism

76/100

Blocked

60%

Avg conflicts / tx

0.82

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #83,904,084  ·  17 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

0x12dd43c9…22d9

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0x5df6102c…6494

0xa6afd3…d132

6 touches
3 conflicts

0x7b7af531…48f1

0xa6afd3…d132

6 touches
3 conflicts

0x213a54fa…c85f

0x34b655…2a6f

4 touches
1 conflict

0x3deac4a2…d2bd

0x34b655…2a6f

4 touches
1 conflict

0x3e505a15…70f8

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 0x12dd43c959…9a22d9

← previous block·next block →recent activity