← previous blocknext block →recent activity

Analyzing

Block #101,321,449

23 transactions · 21 stateful · 2026-09-02 11:53:47 UTC

Parallelism

83/100

Blocked

33%

Avg conflicts / tx

0.57

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #101,321,449  ·  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

0x615bc8cc…15d2

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0xd17580f9…ece1

0x754704…b603

4 touches
1 conflict

0x676b5eb4…0b33

0x34b655…2a6f

4 touches
1 conflict

0x7c2b0f0e…4933

0x34b655…2a6f

4 touches
1 conflict

0x86bd79a5…1f48

0x34b655…2a6f

4 touches
1 conflict

0xb17dddfb…96a2

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

3 conflicts on slot 0x615bc8cc79…5215d2

← previous block·next block →recent activity