← previous blocknext block →recent activity

Analyzing

Block #98,061,507

19 transactions · 19 stateful · 2026-08-22 01:27:42 UTC

Parallelism

84/100

Blocked

26%

Avg conflicts / tx

0.37

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #98,061,507  ·  19 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

0xec162e6c…be77

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xf7eb2a03…d52d

0x34b655…2a6f

4 touches
1 conflict

0xf98db8ee…a56d

0x34b655…2a6f

4 touches
1 conflict

0x703dea24…d38d

0x34b655…2a6f

4 touches
1 conflict

0x72c8aeb2…9921

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0007

0x340143…768f

4 touches
1 conflict

0x7e5ea60a…c4aa

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 0xec162e6c9a…a9be77

← previous block·next block →recent activity