← previous blocknext block →recent activity

Analyzing

Block #99,197,126

25 transactions · 17 stateful · 2026-08-26 01:25:07 UTC

Parallelism

88/100

Blocked

41%

Avg conflicts / tx

0.4

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #99,197,126  ·  25 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

0x961c0cd9…0937

0x34b655…2a6f

6 touches
3 conflicts

0xb1856468…e84f

0x34b655…2a6f

6 touches
3 conflicts

0x2245d13a…9586

0x34b655…2a6f

4 touches
1 conflict

0x48203298…65cb

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x53f7214d…8ec6

0x34b655…2a6f

4 touches
1 conflict

0x57a7cf46…25d0

0x34b655…2a6f

4 touches
1 conflict

0x5a27cf34…ae3b

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 0x961c0cd92c…d10937

← previous block·next block →recent activity