← previous blocknext block →recent activity

Analyzing

Block #84,352,538

20 transactions · 19 stateful · 2026-06-29 00:02:32 UTC

Parallelism

70/100

Blocked

47%

Avg conflicts / tx

0.95

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #84,352,538  ·  20 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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…000b

0x90c374…be45

12 touches
15 conflicts

0x10a2bd5d…ad6d

0x8d1565…6723

12 touches
15 conflicts

0x00000000…000a

0x90c374…be45

12 touches
15 conflicts

0x6ee30d14…7c60

0x336ed4…c59c

8 touches
12 conflicts

0x4be586c5…b94f

0x8d1565…6723

6 touches
3 conflicts

0x9dd81dc4…e3f0

0x336ed4…c59c

6 touches
3 conflicts

0xc9c85b7b…d25c

0x8d1565…6723

6 touches
3 conflicts

0x73d405c0…481e

0x336ed4…c59c

4 touches
4 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: 0x90c3747c…0ebe45

15 conflicts on slot 0x0000000000…00000b

← previous block·next block →recent activity