← previous blocknext block →recent activity

Analyzing

Block #100,750,830

27 transactions · 16 stateful · 2026-08-31 12:02:24 UTC

Parallelism

78/100

Blocked

56%

Avg conflicts / tx

0.44

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #100,750,830  ·  27 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

0x065ff70b…356d

0x40c49f…2af0

6 touches
3 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x40c49f…2af0

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x81716ce9…095f

0x34b655…2a6f

4 touches
1 conflict

0xafb22303…6db2

0x34b655…2a6f

4 touches
1 conflict

0xafb22303…6db3

0x34b655…2a6f

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: 0x40c49f17…d22af0

3 conflicts on slot 0x065ff70bfe…b9356d

← previous block·next block →recent activity