← previous blocknext block →recent activity

Analyzing

Block #102,051,245

22 transactions · 21 stateful · 2026-09-05 01:11:32 UTC

Parallelism

68/100

Blocked

43%

Avg conflicts / tx

1

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #102,051,245  ·  22 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x51fc8795…126f

0x34b655…2a6f

8 touches
6 conflicts

0x045532dd…4b7d

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x5f749304…d1c1

0x34b655…2a6f

6 touches
3 conflicts

0x7dd96c96…7335

0x34b655…2a6f

6 touches
3 conflicts

0x8bf661cb…bcd2

0x34b655…2a6f

6 touches
3 conflicts

0x95500e1e…b52c

0x34b655…2a6f

6 touches
3 conflicts

0x01315072…0e2d

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: Perpl

6 conflicts on slot 0x51fc8795c8…57126f

← previous block·next block →recent activity