← previous blocknext block →recent activity

Analyzing

Block #100,791,331

23 transactions · 18 stateful · 2026-08-31 15:26:20 UTC

Parallelism

87/100

Blocked

28%

Avg conflicts / tx

0.3

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #100,791,331  ·  23 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

0x9e4f30ea…3d07

0x34b655…2a6f

6 touches
3 conflicts

0x3df4a634…c5d4

0x34b655…2a6f

4 touches
1 conflict

0x7462b8f2…6312

0x34b655…2a6f

4 touches
1 conflict

0x823a7ba9…34c9

0x34b655…2a6f

4 touches
1 conflict

0xafb22303…6db2

0x34b655…2a6f

4 touches
1 conflict

0xafb22303…6db3

0x34b655…2a6f

4 touches
1 conflict

0xb20094ed…0fef

0x34b655…2a6f

4 touches
1 conflict

0xbcbf5d09…8bac

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 0x9e4f30ea2f…6d3d07

← previous block·next block →recent activity