← previous blocknext block →recent activity

Analyzing

Block #102,480,009

16 transactions · 16 stateful · 2026-09-06 13:24:21 UTC

Parallelism

81/100

Blocked

38%

Avg conflicts / tx

0.56

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #102,480,009  ·  16 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xb205ab26…a104

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0xd17580f9…ece1

0x754704…b603

4 touches
1 conflict

0x3f5831e5…02b2

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x51fc8795…126f

0x34b655…2a6f

4 touches
1 conflict

0x66d0c4a4…add3

0x34b655…2a6f

4 touches
1 conflict

0x711ceb8d…5202

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

3 conflicts on slot 0xb205ab2626…6fa104

← previous block·next block →recent activity