← previous blocknext block →recent activity

Analyzing

Block #102,005,771

16 transactions · 15 stateful · 2026-09-04 21:21:17 UTC

Parallelism

88/100

Blocked

7%

Avg conflicts / tx

0.06

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #102,005,771  ·  16 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x6823c28e…594c

0x34b655…2a6f

4 touches
1 conflict

0x04d4f30d…4dfb

0x34b655…2a6f

4 touches
1 conflict

0x79ec4509…1f61

0x34b655…2a6f

4 touches
1 conflict

0x8bf661cb…bcd2

0x34b655…2a6f

4 touches
1 conflict

0xf7772b49…fc12

0x34b655…2a6f

4 touches
1 conflict

0x3fb3f2e2…fef3

0x34b655…2a6f

4 touches
1 conflict

0x5746581b…0cb1

0x34b655…2a6f

4 touches
1 conflict

0xdc7b9eda…e616

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 0x6823c28eb2…d0594c

← previous block·next block →recent activity