← previous blocknext block →recent activity

Analyzing

Block #98,272,501

18 transactions · 17 stateful · 2026-08-22 19:09:57 UTC

Parallelism

61/100

Blocked

53%

Avg conflicts / tx

0.83

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #98,272,501  ·  18 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

8 touches
6 conflicts

0x7867ad58…cf21

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xd459bf7b…92c3

0x34b655…2a6f

6 touches
3 conflicts

0xa496748e…8183

0x34b655…2a6f

6 touches
3 conflicts

0x4c29ecd5…58b6

0x34b655…2a6f

4 touches
1 conflict

0x5e3014f0…b4e1

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

6 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity