← previous blocknext block →recent activity

Analyzing

Block #98,027,548

20 transactions · 19 stateful · 2026-08-21 22:36:49 UTC

Parallelism

80/100

Blocked

37%

Avg conflicts / tx

0.4

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #98,027,548  ·  20 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

0x7de57974…f5ba

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0007

0x340143…768f

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x00000000…003d

0xa6afd3…d132

4 touches
1 conflict

0x2b54cadb…4425

0xd18b7e…414b

4 touches
1 conflict

0x1fd77335…9120

0x34b655…2a6f

4 touches
1 conflict

0x4d5af4e3…f90d

0x34b655…2a6f

4 touches
1 conflict

0x5c83897e…aba6

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 0x7de579746e…f0f5ba

← previous block·next block →recent activity