← previous blocknext block →recent activity

Analyzing

Block #84,023,141

29 transactions · 20 stateful · 2026-06-27 11:28:19 UTC

Parallelism

83/100

Blocked

35%

Avg conflicts / tx

0.45

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #84,023,141  ·  29 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

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x9672a430…3356

0x34b655…2a6f

6 touches
3 conflicts

0x9dbefc67…4855

0x34b655…2a6f

6 touches
3 conflicts

0x8a5efe9a…fa31

0x34b655…2a6f

6 touches
3 conflicts

0x444c3ac5…2a12

0x34b655…2a6f

6 touches
3 conflicts

0x9ff4ca89…6115

0x34b655…2a6f

4 touches
1 conflict

0xa87b10e5…6293

0x34b655…2a6f

4 touches
1 conflict

0xb6b7c45d…9d5a

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

10 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity