← previous blocknext block →recent activity

Analyzing

Block #84,061,216

20 transactions · 17 stateful · 2026-06-27 15:41:59 UTC

Parallelism

75/100

Blocked

41%

Avg conflicts / tx

0.75

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #84,061,216  ·  20 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

0x737acb78…fce8

0x34b655…2a6f

8 touches
6 conflicts

0xac2a0273…721b

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xbeb10b8a…4ce5

0x34b655…2a6f

6 touches
3 conflicts

0xb3fb9fb5…64dc

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0002

0xd637b3…4160

4 touches
1 conflict

0x3b0a8356…a2b6

0x34b655…2a6f

4 touches
1 conflict

0x52df4e8f…0b7f

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 0x737acb7813…fafce8

← previous block·next block →recent activity