← previous blocknext block →recent activity

Analyzing

Block #84,032,916

29 transactions · 18 stateful · 2026-06-27 12:33:21 UTC

Parallelism

86/100

Blocked

22%

Avg conflicts / tx

0.24

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #84,032,916  ·  29 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

0x99a3a7c1…1e2b

0x0cc9b2…7777

8 touches
6 conflicts

0xa10c86f8…4b74

0x3bd359…433a

8 touches
6 conflicts

0xa472d565…9fe4

0x3bd359…433a

8 touches
6 conflicts

0x00000000…0000

0x019883…2a9a

8 touches
6 conflicts

0x00000000…0002

0x019883…2a9a

8 touches
6 conflicts

0x00000000…0003

0x019883…2a9a

8 touches
6 conflicts

0x44ad89ba…cf83

0x0cc9b2…7777

8 touches
6 conflicts

0x9a555477…19a8

0x754704…b603

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: MONI (MONI)

6 conflicts on slot 0x99a3a7c17c…081e2b

← previous block·next block →recent activity