← previous blocknext block →recent activity

Analyzing

Block #84,361,045

24 transactions · 16 stateful · 2026-06-29 00:59:18 UTC

Parallelism

88/100

Blocked

38%

Avg conflicts / tx

0.42

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #84,361,045  ·  24 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

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x0dbe1328…cc93

0x065c9d…c394

5 touches
3 conflicts

0x619f5683…5bd4

0x34b655…2a6f

4 touches
1 conflict

0x7d42dc8b…fdb6

0x2a68ba…90c5

4 touches
1 conflict

0x3f4dc602…5a18

0x34b655…2a6f

4 touches
1 conflict

0x59f38ee1…afd3

0x34b655…2a6f

4 touches
1 conflict

0x9966da31…0d0f

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

3 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity