← previous blocknext block →recent activity

Analyzing

Block #84,352,546

19 transactions · 17 stateful · 2026-06-29 00:02:35 UTC

Parallelism

84/100

Blocked

35%

Avg conflicts / tx

0.47

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #84,352,546  ·  19 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

0x454d8940…cfe7

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x1dc530be…8afa

0x34b655…2a6f

4 touches
1 conflict

0x227f5d53…e0b2

0x34b655…2a6f

4 touches
1 conflict

0x2cb897e4…21ea

0x34b655…2a6f

4 touches
1 conflict

0x5c8d0f1e…049d

0x34b655…2a6f

4 touches
1 conflict

0x7425a853…a582

0x34b655…2a6f

4 touches
1 conflict

0x76ed8777…1e5f

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 0x454d8940c1…fbcfe7

← previous block·next block →recent activity