← previous blocknext block →recent activity

Analyzing

Block #99,493,615

18 transactions · 18 stateful · 2026-08-27 02:17:36 UTC

Parallelism

72/100

Blocked

44%

Avg conflicts / tx

0.83

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #99,493,615  ·  18 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

0xf081c170…f590

0x34b655…2a6f

10 touches
10 conflicts

0x2202504e…fad0

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x4c29ecd5…58b6

0x34b655…2a6f

6 touches
3 conflicts

0xac0b4a08…faae

0x34b655…2a6f

6 touches
3 conflicts

0xe1c4e5ce…0dec

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x9210e826…1414

0x34b655…2a6f

6 touches
3 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

10 conflicts on slot 0xf081c1706e…86f590

← previous block·next block →recent activity