← previous blocknext block →recent activity

Analyzing

Block #83,637,268

16 transactions · 14 stateful · 2026-06-25 16:34:56 UTC

Parallelism

75/100

Blocked

50%

Avg conflicts / tx

0.69

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #83,637,268  ·  16 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xaa7ee7…f0e4

8 touches
6 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

6 touches
3 conflicts

0x793aa64d…b09d

0x34b655…2a6f

4 touches
1 conflict

0xb577a4a7…a670

0x34b655…2a6f

4 touches
1 conflict

0x1b925784…660d

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x5d7f309d…5145

0x34b655…2a6f

4 touches
1 conflict

0x1d4b0baf…1423

0x34b655…2a6f

3 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: 0xaa7ee7ce…aff0e4

6 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity