← previous blocknext block →recent activity

Analyzing

Block #102,414,232

20 transactions · 20 stateful · 2026-09-06 07:51:05 UTC

Parallelism

75/100

Blocked

30%

Avg conflicts / tx

0.7

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #102,414,232  ·  20 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x22f10271…841d

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xfe39a1f7…8eb0

0x34b655…2a6f

4 touches
1 conflict

0x42e5184f…4e8c

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x4bfc3595…2d5a

0x34b655…2a6f

4 touches
1 conflict

0xa3dee461…96b8

0x34b655…2a6f

4 touches
1 conflict

0xbceecf11…0120

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 0x22f10271ce…96841d

← previous block·next block →recent activity