← previous blocknext block →recent activity

Analyzing

Block #102,800,189

27 transactions · 24 stateful · 2026-09-07 16:23:56 UTC

Parallelism

78/100

Blocked

33%

Avg conflicts / tx

0.7

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #102,800,189  ·  27 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xe58b0a60…54a1

0x40c49f…2af0

12 touches
15 conflicts

0x002fed35…79fa

0x2a68ba…90c5

12 touches
15 conflicts

0x2b54cadb…4425

0xd18b7e…414b

8 touches
6 conflicts

0xa1087a5c…66c4

0x754704…b603

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x55010ec8…ea31

0x34b655…2a6f

6 touches
3 conflicts

0xe3d92175…b97e

0x34b655…2a6f

6 touches
3 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 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: 0x40c49f17…d22af0

15 conflicts on slot 0xe58b0a606b…fb54a1

← previous block·next block →recent activity