← previous blocknext block →recent activity

Analyzing

Block #98,379,290

17 transactions · 16 stateful · 2026-08-23 04:07:14 UTC

Parallelism

71/100

Blocked

44%

Avg conflicts / tx

0.76

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #98,379,290  ·  17 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x482471ad…122f

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0x8f84702c…c5f9

0x34b655…2a6f

8 touches
6 conflicts

0xbb97db90…4c93

0xc8689a…ee79

4 touches
1 conflict

0x3bba5a42…2e84

0x34b655…2a6f

4 touches
1 conflict

0x5f5cb57b…8dcf

0x34b655…2a6f

4 touches
1 conflict

0x676f9f01…a8ac

0x34b655…2a6f

4 touches
1 conflict

0x90a021f0…f922

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

10 conflicts on slot 0x482471adbb…39122f

← previous block·next block →recent activity