← previous blocknext block →recent activity

Analyzing

Block #101,664,706

16 transactions · 15 stateful · 2026-09-03 16:40:49 UTC

Parallelism

81/100

Blocked

27%

Avg conflicts / tx

0.38

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #101,664,706  ·  16 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

0xec7d120d…7084

0x34b655…2a6f

6 touches
3 conflicts

0x021cd478…a6d4

0x34b655…2a6f

4 touches
1 conflict

0x3732c6c9…ded6

0x34b655…2a6f

4 touches
1 conflict

0x4387ba94…e195

0x34b655…2a6f

4 touches
1 conflict

0x72cea714…3b4c

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

0x34b655…2a6f

4 touches
1 conflict

0x88875dc5…ecc6

0x34b655…2a6f

4 touches
1 conflict

0xca841faa…486a

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 0xec7d120df9…5d7084

← previous block·next block →recent activity