← previous blocknext block →recent activity

Analyzing

Block #101,802,373

17 transactions · 16 stateful · 2026-09-04 04:13:16 UTC

Parallelism

65/100

Blocked

50%

Avg conflicts / tx

0.88

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #101,802,373  ·  17 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x7849366c…8914

0x34b655…2a6f

8 touches
6 conflicts

0x0b0611f7…e63a

0x34b655…2a6f

6 touches
3 conflicts

0xdc8d7edd…8a03

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x51fc8795…126f

0x34b655…2a6f

6 touches
3 conflicts

0xd74aff4b…c4d2

0x34b655…2a6f

4 touches
1 conflict

0x4dffc33e…068d

0x34b655…2a6f

4 touches
1 conflict

0x4f3cc09a…2804

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

6 conflicts on slot 0x7849366c03…548914

← previous block·next block →recent activity