← previous blocknext block →recent activity

Analyzing

Block #100,583,379

42 transactions · 30 stateful · 2026-08-30 22:00:04 UTC

Parallelism

76/100

Blocked

50%

Avg conflicts / tx

1.33

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #100,583,379  ·  42 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0x474e5df9…821f

0x851145…3f07

20 touches
45 conflicts

0xebb1466a…d86a

0x851145…3f07

19 touches
45 conflicts

0xf7640726…19a2

0x2a68ba…90c5

18 touches
36 conflicts

0x08d53462…97ef

0x2b46c0…1669

18 touches
36 conflicts

0x002fed35…79fa

0x2a68ba…90c5

18 touches
36 conflicts

0x889d5e90…929a

0x2a68ba…90c5

18 touches
36 conflicts

0x80caf0f7…f2de

0x2b46c0…1669

18 touches
36 conflicts

0xd8fd2add…50fc

0x2b46c0…1669

18 touches
36 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: 0x851145ea…9f3f07

45 conflicts on slot 0x474e5df9d7…a5821f

← previous block·next block →recent activity