← previous blocknext block →recent activity

Analyzing

Block #102,221,998

28 transactions · 25 stateful · 2026-09-05 15:37:00 UTC

Parallelism

86/100

Blocked

20%

Avg conflicts / tx

0.36

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #102,221,998  ·  28 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x20b94f7c…2a9b

0x34b655…2a6f

6 touches
3 conflicts

0x6e7eb884…4fab

0x34b655…2a6f

4 touches
1 conflict

0xb8490420…2c54

0x34b655…2a6f

4 touches
1 conflict

0xc852b267…9d14

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xaad6be10…0801

0x2a68ba…90c5

4 touches
1 conflict

0x482471ad…122f

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

6 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity