← previous blocknext block →recent activity

Analyzing

Block #102,436,159

17 transactions · 16 stateful · 2026-09-06 09:42:11 UTC

Parallelism

53/100

Blocked

63%

Avg conflicts / tx

1.41

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #102,436,159  ·  17 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

0x00000000…00c9

0x34b655…2a6f

10 touches
10 conflicts

0xca841faa…486a

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…641f

0x34b655…2a6f

8 touches
6 conflicts

0xbceecf11…0120

0x34b655…2a6f

6 touches
3 conflicts

0x6c28863e…840e

0x34b655…2a6f

6 touches
3 conflicts

0x42e5184f…4e8b

0x34b655…2a6f

6 touches
3 conflicts

0x0a6f5e37…6c3c

0x34b655…2a6f

6 touches
3 conflicts

0x3ca10617…ef02

0x34b655…2a6f

5 touches
3 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

10 conflicts on slot 0x0000000000…0000c9

← previous block·next block →recent activity