← previous blocknext block →recent activity

Analyzing

Block #99,192,405

18 transactions · 18 stateful · 2026-08-26 01:01:23 UTC

Parallelism

78/100

Blocked

44%

Avg conflicts / tx

0.78

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #99,192,405  ·  18 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

0xd9722304…6ed0

0x34b655…2a6f

8 touches
6 conflicts

0xe251ba03…50f8

0x34b655…2a6f

6 touches
3 conflicts

0x20b12e82…67dc

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x72b221b7…d89b

0x34b655…2a6f

4 touches
1 conflict

0x746bcce3…d0ce

0x34b655…2a6f

4 touches
1 conflict

0x7de57974…f5ba

0x34b655…2a6f

4 touches
1 conflict

0x89ac61bf…9443

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 0xd97223041d…366ed0

← previous block·next block →recent activity