← previous blocknext block →recent activity

Analyzing

Block #101,854,361

18 transactions · 16 stateful · 2026-09-04 08:34:46 UTC

Parallelism

67/100

Blocked

44%

Avg conflicts / tx

1

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #101,854,361  ·  18 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

0xc824469a…6425

0x34b655…2a6f

12 touches
15 conflicts

0x482471ad…122f

0x34b655…2a6f

12 touches
15 conflicts

0x85eb1316…bb9e

0x34b655…2a6f

6 touches
3 conflicts

0x7c93b38a…9e69

0x34b655…2a6f

6 touches
3 conflicts

0x74eb24d4…f0c7

0x34b655…2a6f

6 touches
3 conflicts

0x735a86cd…b64d

0x34b655…2a6f

4 touches
1 conflict

0x7e06d07b…36af

0x34b655…2a6f

4 touches
1 conflict

0x7e06d07b…36b0

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

15 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity