← previous blocknext block →recent activity

Analyzing

Block #101,921,950

23 transactions · 22 stateful · 2026-09-04 14:15:57 UTC

Parallelism

74/100

Blocked

36%

Avg conflicts / tx

0.52

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #101,921,950  ·  23 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

6 touches
3 conflicts

0xda09bbc9…b41b

0x34b655…2a6f

6 touches
3 conflicts

0xe53bd661…5352

0x34b655…2a6f

6 touches
3 conflicts

0x53e08444…d671

0x34b655…2a6f

6 touches
3 conflicts

0x8bf661cb…bcd2

0x34b655…2a6f

6 touches
3 conflicts

0x02372d42…1871

0x34b655…2a6f

6 touches
3 conflicts

0x7c216fca…20cb

0x34b655…2a6f

4 touches
1 conflict

0x81035be8…65b8

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

← previous block·next block →recent activity