← previous blocknext block →recent activity

Analyzing

Block #101,491,742

22 transactions · 21 stateful · 2026-09-03 02:10:42 UTC

Parallelism

86/100

Blocked

24%

Avg conflicts / tx

0.27

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #101,491,742  ·  22 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x6cda5bc9…8e0e

0x34b655…2a6f

4 touches
1 conflict

0x92bb4e9d…0f03

0x34b655…2a6f

4 touches
1 conflict

0x94dabb65…43a3

0x34b655…2a6f

4 touches
1 conflict

0xaff3c28d…9e37

0x34b655…2a6f

4 touches
1 conflict

0xbde524f4…43bf

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x851145…3f07

4 touches
1 conflict

0x477cb4f5…11b4

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

1 conflict on slot 0x6cda5bc95a…078e0e

← previous block·next block →recent activity