← previous blocknext block →recent activity

Analyzing

Block #102,395,653

19 transactions · 17 stateful · 2026-09-06 06:16:59 UTC

Parallelism

84/100

Blocked

41%

Avg conflicts / tx

0.47

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #102,395,653  ·  19 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

0xa4e9800f…4ab0

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x56a284d9…32e4

0x34b655…2a6f

6 touches
3 conflicts

0xcd26fba5…21c6

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…641f

0x34b655…2a6f

6 touches
3 conflicts

0xefad5569…e5ec

0x34b655…2a6f

5 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

4 touches
1 conflict

0x886db264…846e

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 0xa4e9800f4e…fc4ab0

← previous block·next block →recent activity