← previous blocknext block →recent activity

Analyzing

Block #84,360,222

23 transactions · 16 stateful · 2026-06-29 00:53:50 UTC

Parallelism

87/100

Blocked

38%

Avg conflicts / tx

0.26

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #84,360,222  ·  23 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

0x00000000…0002

0xd637b3…4160

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x85af7d5a…3d0f

0x34b655…2a6f

4 touches
1 conflict

0x8a7af3fd…72a7

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xf7468e81…86e5

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0xa6afd3…d132

4 touches
1 conflict

0x2a2708bf…f287

0xa6afd3…d132

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: 0xd637b38f…c64160

1 conflict on slot 0x0000000000…000002

← previous block·next block →recent activity