← previous blocknext block →recent activity

Analyzing

Block #101,992,912

17 transactions · 15 stateful · 2026-09-04 20:16:01 UTC

Parallelism

82/100

Blocked

27%

Avg conflicts / tx

0.29

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #101,992,912  ·  17 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

0x65903ef9…2567

0x34b655…2a6f

6 touches
3 conflicts

0x172b0de5…980b

0x34b655…2a6f

4 touches
1 conflict

0x3c67d31e…3dbe

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x483c2974…bee4

0x34b655…2a6f

4 touches
1 conflict

0x56e0d685…c960

0x34b655…2a6f

4 touches
1 conflict

0x5746581b…0cb1

0x34b655…2a6f

4 touches
1 conflict

0x6823c28e…594c

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 0x65903ef9a0…7d2567

← previous block·next block →recent activity