← previous blocknext block →recent activity

Analyzing

Block #101,970,688

24 transactions · 22 stateful · 2026-09-04 18:23:14 UTC

Parallelism

71/100

Blocked

41%

Avg conflicts / tx

0.79

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #101,970,688  ·  24 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

0x045532dd…4b7d

0x34b655…2a6f

8 touches
6 conflicts

0x8bf661cb…bcd2

0x34b655…2a6f

8 touches
6 conflicts

0xb639a57c…a08a

0x34b655…2a6f

8 touches
6 conflicts

0x51fc8795…126f

0x34b655…2a6f

8 touches
6 conflicts

0xfa805f95…72a4

0x34b655…2a6f

6 touches
3 conflicts

0x04d4f30d…4dfb

0x34b655…2a6f

6 touches
3 conflicts

0x32e1d03e…68a7

0x34b655…2a6f

6 touches
3 conflicts

0x3fb3f2e2…fef3

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 0x045532dd4b…244b7d

← previous block·next block →recent activity