← previous blocknext block →recent activity

Analyzing

Block #100,567,739

9 transactions · 7 stateful · 2026-08-30 20:41:24 UTC

Parallelism

78/100

Blocked

29%

Avg conflicts / tx

0.22

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #100,567,739  ·  9 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x5d8975d1…341a

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xd814f518…f5b4

0x34b655…2a6f

4 touches
1 conflict

0x09106a95…1467

0x33176b…e078

2 touches
0 conflicts

0x086bb9b5…ce56

0x34b655…2a6f

2 touches
0 conflicts

0x0ec34d4f…5fa1

0x34b655…2a6f

2 touches
0 conflicts

0x207e9f25…4724

0x34b655…2a6f

2 touches
0 conflicts

0x207e9f25…4725

0x34b655…2a6f

2 touches
0 conflicts

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

1 conflict on slot 0x5d8975d1c1…73341a

← previous block·next block →recent activity