← previous blocknext block →recent activity

Analyzing

Block #101,681,090

25 transactions · 22 stateful · 2026-09-03 18:03:15 UTC

Parallelism

80/100

Blocked

36%

Avg conflicts / tx

0.44

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #101,681,090  ·  25 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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x51fc8795…126f

0x34b655…2a6f

6 touches
3 conflicts

0xbde524f4…43bf

0x34b655…2a6f

6 touches
3 conflicts

0xe27f0cad…c122

0x34b655…2a6f

4 touches
1 conflict

0x1aa85bda…e324

0x34b655…2a6f

4 touches
1 conflict

0x6771eae2…7014

0x34b655…2a6f

4 touches
1 conflict

0x6c8f55db…27b0

0x34b655…2a6f

4 touches
1 conflict

0x76ed17bf…9bd8

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity