← previous blocknext block →recent activity

Analyzing

Block #84,354,765

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

Parallelism

74/100

Blocked

42%

Avg conflicts / tx

0.79

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #84,354,765  ·  19 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

0x00000000…0002

0xd637b3…4160

10 touches
10 conflicts

0x00000000…003d

0x40c49f…2af0

6 touches
3 conflicts

0xa9db7b4d…2957

0x40c49f…2af0

4 touches
1 conflict

0xdfc5f346…7b42

0x40c49f…2af0

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x5b571ba0…f13a

0x368ee5…7ca4

2 touches
0 conflicts

0x68faa0b9…14af

0x368ee5…7ca4

2 touches
0 conflicts

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

10 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity