← previous blocknext block →recent activity

Analyzing

Block #98,584,097

24 transactions · 17 stateful · 2026-08-23 21:33:53 UTC

Parallelism

92/100

Blocked

29%

Avg conflicts / tx

0.21

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #98,584,097  ·  24 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x4e5afb3a…a338

0x3bd359…433a

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x0fb999ce…da22

0x754704…b603

4 touches
1 conflict

0xff53b6b2…2f57

0x754704…b603

4 touches
1 conflict

0x00000000…0002

0xbb3f3c…e046

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x48ed1159…abe9

0x2b46c0…1669

2 touches
0 conflicts

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity