← previous blocknext block →recent activity

Analyzing

Block #101,674,895

17 transactions · 16 stateful · 2026-09-03 17:32:05 UTC

Parallelism

82/100

Blocked

38%

Avg conflicts / tx

0.65

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #101,674,895  ·  17 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

0xdac8e13c…bc65

0x34b655…2a6f

6 touches
3 conflicts

0xe1c4e5ce…0dec

0x34b655…2a6f

6 touches
3 conflicts

0xe3777c4e…44f8

0x34b655…2a6f

6 touches
3 conflicts

0xe8f860c0…35c9

0x34b655…2a6f

6 touches
3 conflicts

0x3fb3f2e2…fef3

0x34b655…2a6f

6 touches
3 conflicts

0x3d13406e…eff1

0x34b655…2a6f

6 touches
3 conflicts

0x4dffc33e…068d

0x34b655…2a6f

6 touches
3 conflicts

0x8bf661cb…bcd2

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

3 conflicts on slot 0xdac8e13c56…48bc65

← previous block·next block →recent activity