← previous blocknext block →recent activity

Analyzing

Block #102,854,934

22 transactions · 19 stateful · 2026-09-07 20:59:33 UTC

Parallelism

73/100

Blocked

42%

Avg conflicts / tx

0.86

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #102,854,934  ·  22 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

0x470b41f6…fc68

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0x5f2cf00e…8604

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x84fb2a36…db89

0x34b655…2a6f

4 touches
1 conflict

0xd17580f9…ece1

0x754704…b603

4 touches
1 conflict

0x045532dd…4b7d

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

10 conflicts on slot 0x470b41f691…2dfc68

← previous block·next block →recent activity