← previous blocknext block →recent activity

Analyzing

Block #100,984,296

27 transactions · 21 stateful · 2026-09-01 07:37:12 UTC

Parallelism

81/100

Blocked

33%

Avg conflicts / tx

0.48

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #100,984,296  ·  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

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0xded216ce…191a

0xa6afd3…d132

4 touches
1 conflict

0x0dd3d3cd…7281

0x34b655…2a6f

4 touches
1 conflict

0x641aed07…bcb9

0x34b655…2a6f

4 touches
1 conflict

0x675c8b75…6e4f

0x34b655…2a6f

4 touches
1 conflict

0x6ca15e14…7be8

0x34b655…2a6f

4 touches
1 conflict

0xfa09be5a…1e79

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

10 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity