← previous blocknext block →recent activity

Analyzing

Block #101,800,793

17 transactions · 17 stateful · 2026-09-04 04:05:19 UTC

Parallelism

71/100

Blocked

41%

Avg conflicts / tx

0.94

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #101,800,793  ·  17 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

0xca841faa…486a

0x34b655…2a6f

10 touches
10 conflicts

0x51fc8795…126f

0x34b655…2a6f

6 touches
3 conflicts

0x2d94ecd9…43db

0x34b655…2a6f

4 touches
1 conflict

0xd18b9ae9…9753

0x34b655…2a6f

4 touches
1 conflict

0xe7fa4f4d…a2e4

0x34b655…2a6f

4 touches
1 conflict

0xbde524f4…43bf

0x34b655…2a6f

4 touches
1 conflict

0x5086c64a…28ba

0x34b655…2a6f

4 touches
1 conflict

0x2dbb83fd…bd07

0x34b655…2a6f

2 touches
0 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

10 conflicts on slot 0xca841faae5…71486a

← previous block·next block →recent activity