← previous blocknext block →recent activity

Analyzing

Block #102,739,348

43 transactions · 36 stateful · 2026-09-07 11:14:47 UTC

Parallelism

72/100

Blocked

69%

Avg conflicts / tx

1.6

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #102,739,348  ·  43 txs across 12 waves  ·  depth 12
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

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

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0xaad6be10…0801

0x2a68ba…90c5

12 touches
15 conflicts

0x00000000…003d

0x065c9d…c394

12 touches
15 conflicts

0xa605468c…1bfc

0x34ae4d…3fc5

8 touches
6 conflicts

0xcc4f1f14…aa5f

0x065c9d…c394

8 touches
6 conflicts

0xb87af72a…aef6

0x2a68ba…90c5

8 touches
6 conflicts

0x06e40499…165e

0x34ae4d…3fc5

8 touches
6 conflicts

0xa1087a5c…66c4

0x754704…b603

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

15 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity