← previous blocknext block →recent activity

Analyzing

Block #99,848,494

20 transactions · 18 stateful · 2026-08-28 08:16:52 UTC

Parallelism

80/100

Blocked

50%

Avg conflicts / tx

0.7

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #99,848,494  ·  20 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

0x89656ac5…5173

0x34b655…2a6f

6 touches
3 conflicts

0x3c67d31e…3dbe

0x34b655…2a6f

6 touches
3 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x851145…3f07

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x758a0dd5…0f46

0x34b655…2a6f

4 touches
1 conflict

0x9a7631b1…4f23

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