← previous blocknext block →recent activity

Analyzing

Block #99,212,213

17 transactions · 17 stateful · 2026-08-26 02:41:01 UTC

Parallelism

82/100

Blocked

35%

Avg conflicts / tx

0.53

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #99,212,213  ·  17 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

0x78860c4f…cade

0x34b655…2a6f

6 touches
3 conflicts

0x2d5ed09e…32a2

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xac808a27…82db

0x34b655…2a6f

4 touches
1 conflict

0x348fda08…7e96

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x11258774…9892

0x2a68ba…90c5

4 touches
1 conflict

0x42522e76…2592

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 0x78860c4feb…4dcade

← previous block·next block →recent activity