← previous blocknext block →recent activity

Analyzing

Block #100,612,088

24 transactions · 19 stateful · 2026-08-31 00:24:30 UTC

Parallelism

83/100

Blocked

37%

Avg conflicts / tx

0.33

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #100,612,088  ·  24 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

0x15698ac9…2a46

0x34b655…2a6f

6 touches
3 conflicts

0xf3d10975…0d07

0x34b655…2a6f

4 touches
1 conflict

0x2c0c3e3f…5849

0x34b655…2a6f

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x41469894…598f

0x34b655…2a6f

4 touches
1 conflict

0x41469894…5990

0x34b655…2a6f

4 touches
1 conflict

0x00000000…004f

0x80c745…7210

4 touches
1 conflict

0xa242e227…2e45

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 0x15698ac9db…df2a46

← previous block·next block →recent activity