← previous blocknext block →recent activity

Analyzing

Block #98,064,444

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

Parallelism

85/100

Blocked

32%

Avg conflicts / tx

0.3

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #98,064,444  ·  20 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

0xe1c4e5ce…0dec

0x34b655…2a6f

4 touches
1 conflict

0x41be9e75…9773

0x34b655…2a6f

4 touches
1 conflict

0x517aba30…459c

0x34b655…2a6f

4 touches
1 conflict

0x7de57974…f5ba

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

0x34b655…2a6f

4 touches
1 conflict

0xb0f5d668…99ac

0x34b655…2a6f

4 touches
1 conflict

0xbc8fb280…76a3

0x34b655…2a6f

4 touches
1 conflict

0xbd590df7…9891

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

1 conflict on slot 0xe1c4e5ce15…770dec

← previous block·next block →recent activity