← previous blocknext block →recent activity

Analyzing

Block #101,969,404

18 transactions · 18 stateful · 2026-09-04 18:16:45 UTC

Parallelism

67/100

Blocked

44%

Avg conflicts / tx

0.78

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #101,969,404  ·  18 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

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x51fc8795…126f

0x34b655…2a6f

8 touches
6 conflicts

0xc0f6895c…e428

0x34b655…2a6f

6 touches
3 conflicts

0x7dd96c96…7335

0x34b655…2a6f

6 touches
3 conflicts

0xe8f860c0…35c9

0x34b655…2a6f

6 touches
3 conflicts

0xfcd7574f…a3a2

0x34b655…2a6f

6 touches
3 conflicts

0x8bf661cb…bcd2

0x34b655…2a6f

6 touches
3 conflicts

0x04d4f30d…4dfb

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity