← previous blocknext block →recent activity

Analyzing

Block #102,345,564

22 transactions · 20 stateful · 2026-09-06 02:03:16 UTC

Parallelism

77/100

Blocked

35%

Avg conflicts / tx

0.55

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #102,345,564  ·  22 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

0xfb682e7d…dde9

0x34b655…2a6f

6 touches
3 conflicts

0x733c7779…a647

0x34b655…2a6f

6 touches
3 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0xbde524f4…43bf

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x30c5329c…711c

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x5e782d17…5317

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 0xfb682e7d8c…dcdde9

← previous block·next block →recent activity