← previous blocknext block →recent activity

Analyzing

Block #100,979,037

21 transactions · 20 stateful · 2026-09-01 07:10:45 UTC

Parallelism

81/100

Blocked

35%

Avg conflicts / tx

0.52

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #100,979,037  ·  21 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xfc2493d3…6898

0x34b655…2a6f

4 touches
1 conflict

0x5e8223c2…c242

0x34b655…2a6f

4 touches
1 conflict

0x2d071de0…c86e

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x8b7fe709…9d99

0x34b655…2a6f

4 touches
1 conflict

0x5d3c6659…4467

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

6 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity