← previous blocknext block →recent activity

Analyzing

Block #102,043,979

23 transactions · 22 stateful · 2026-09-05 00:34:41 UTC

Parallelism

70/100

Blocked

41%

Avg conflicts / tx

0.83

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #102,043,979  ·  23 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

0xe8f860c0…35c9

0x34b655…2a6f

8 touches
6 conflicts

0x2f17174f…68b4

0x34b655…2a6f

8 touches
6 conflicts

0x65f011a5…bc6e

0x34b655…2a6f

8 touches
6 conflicts

0x8bf661cb…bcd2

0x34b655…2a6f

8 touches
6 conflicts

0x8feb2121…031a

0x34b655…2a6f

8 touches
6 conflicts

0x9d7ac3b9…22f8

0x34b655…2a6f

8 touches
6 conflicts

0xa735de1d…29b0

0x34b655…2a6f

8 touches
6 conflicts

0xb826ef15…d248

0x34b655…2a6f

8 touches
6 conflicts

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 0xe8f860c039…3435c9

← previous block·next block →recent activity