← previous blocknext block →recent activity

Analyzing

Block #102,043,810

23 transactions · 20 stateful · 2026-09-05 00:33:50 UTC

Parallelism

83/100

Blocked

30%

Avg conflicts / tx

0.48

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #102,043,810  ·  23 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

8 touches
6 conflicts

0x1b62550e…f9a8

0x34b655…2a6f

4 touches
1 conflict

0x1d1eb3d2…d573

0x34b655…2a6f

4 touches
1 conflict

0x48828733…fd48

0x34b655…2a6f

4 touches
1 conflict

0x6636a104…d595

0x34b655…2a6f

4 touches
1 conflict

0x6c28863e…840e

0x34b655…2a6f

4 touches
1 conflict

0x750b76f7…040d

0x34b655…2a6f

4 touches
1 conflict

0x97394169…cfc0

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

6 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity