← previous blocknext block →recent activity

Analyzing

Block #100,143,938

27 transactions · 22 stateful · 2026-08-29 09:05:09 UTC

Parallelism

81/100

Blocked

41%

Avg conflicts / tx

0.48

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #100,143,938  ·  27 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xfcea499d…d54d

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0xf98c943e…7c44

0x34b655…2a6f

6 touches
3 conflicts

0x0efc210e…70ab

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x508c6c07…14f2

0x34b655…2a6f

4 touches
1 conflict

0x6b267bdf…b173

0x34b655…2a6f

4 touches
1 conflict

0x83f3d320…fb59

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 0xfcea499dcb…2cd54d

← previous block·next block →recent activity