← previous blocknext block →recent activity

Analyzing

Block #100,029,971

17 transactions · 16 stateful · 2026-08-28 23:31:15 UTC

Parallelism

82/100

Blocked

38%

Avg conflicts / tx

0.53

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #100,029,971  ·  17 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xca2b4ab7…5236

0x34b655…2a6f

6 touches
3 conflicts

0xd3e6afcd…12b6

0x34b655…2a6f

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x21d102c4…7f30

0x34b655…2a6f

4 touches
1 conflict

0x35b89cd8…5092

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x49890ced…6f23

0x34b655…2a6f

4 touches
1 conflict

0x51cfbcbc…fa29

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: Perpl

3 conflicts on slot 0xca2b4ab77a…6e5236

← previous block·next block →recent activity