← previous blocknext block →recent activity

Analyzing

Block #102,641,295

24 transactions · 23 stateful · 2026-09-07 03:01:28 UTC

Parallelism

67/100

Blocked

35%

Avg conflicts / tx

0.75

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #102,641,295  ·  24 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x46c14e01…ff09

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xca841faa…486a

0x34b655…2a6f

8 touches
6 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

8 touches
6 conflicts

0x326a02b5…8dad

0x34b655…2a6f

6 touches
3 conflicts

0x6fbc2e5a…e69c

0x34b655…2a6f

6 touches
3 conflicts

0x3c67d31e…3dbe

0x34b655…2a6f

4 touches
1 conflict

0xff462e14…a60c

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 0x46c14e01c8…d5ff09

← previous block·next block →recent activity