← previous blocknext block →recent activity

Analyzing

Block #101,658,653

24 transactions · 20 stateful · 2026-09-03 16:10:22 UTC

Parallelism

71/100

Blocked

45%

Avg conflicts / tx

0.67

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #101,658,653  ·  24 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xca841faa…486a

0x34b655…2a6f

10 touches
10 conflicts

0x024b482b…16b0

0x34b655…2a6f

4 touches
1 conflict

0x1a2e73cf…5ff5

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x3027f5b0…7a3f

0x34b655…2a6f

4 touches
1 conflict

0x3d13406e…eff1

0x34b655…2a6f

4 touches
1 conflict

0x4c2ea9d0…2aca

0x34b655…2a6f

4 touches
1 conflict

0x4dffc33e…068d

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 0xca841faae5…71486a

← previous block·next block →recent activity