← previous blocknext block →recent activity

Analyzing

Block #101,894,745

18 transactions · 18 stateful · 2026-09-04 11:58:05 UTC

Parallelism

72/100

Blocked

44%

Avg conflicts / tx

0.67

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #101,894,745  ·  18 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xbde524f4…43bf

0x34b655…2a6f

6 touches
3 conflicts

0xaa3b4402…74e6

0x34b655…2a6f

6 touches
3 conflicts

0x045532dd…4b7d

0x34b655…2a6f

4 touches
1 conflict

0x08c5d8d8…c7c1

0x34b655…2a6f

4 touches
1 conflict

0x0ec07cf7…c0c9

0x34b655…2a6f

4 touches
1 conflict

0x51fc8795…126f

0x34b655…2a6f

4 touches
1 conflict

0x67043b0b…97d7

0x34b655…2a6f

4 touches
1 conflict

0x73ae20cb…19f1

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 0xbde524f475…b143bf

← previous block·next block →recent activity