← previous blocknext block →recent activity

Analyzing

Block #101,802,406

13 transactions · 12 stateful · 2026-09-04 04:13:26 UTC

Parallelism

69/100

Blocked

33%

Avg conflicts / tx

0.69

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #101,802,406  ·  13 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

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x51fc8795…126f

0x34b655…2a6f

4 touches
1 conflict

0x5ed07c7e…69aa

0x34b655…2a6f

4 touches
1 conflict

0x5efd7300…d8a5

0x34b655…2a6f

4 touches
1 conflict

0x6352bcf7…67ec

0x34b655…2a6f

4 touches
1 conflict

0x711ceb8d…5202

0x34b655…2a6f

4 touches
1 conflict

0x731d7308…fd26

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

6 conflicts on slot 0x482471adbb…39122f

← previous block·next block →recent activity