← previous blocknext block →recent activity

Analyzing

Block #84,025,749

23 transactions · 19 stateful · 2026-06-27 11:45:42 UTC

Parallelism

78/100

Blocked

37%

Avg conflicts / tx

0.57

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #84,025,749  ·  23 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x4e1ce17e…98a7

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xffc2f21e…b393

0x34b655…2a6f

8 touches
6 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

8 touches
6 conflicts

0x6f1a10f8…5a04

0x34b655…2a6f

6 touches
3 conflicts

0x3a65dc83…7aea

0x34b655…2a6f

4 touches
1 conflict

0x571cb36d…3b3d

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

6 conflicts on slot 0x4e1ce17e14…ed98a7

← previous block·next block →recent activity