← previous blocknext block →recent activity

Analyzing

Block #98,000,158

21 transactions · 18 stateful · 2026-08-21 20:18:42 UTC

Parallelism

81/100

Blocked

39%

Avg conflicts / tx

0.52

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #98,000,158  ·  21 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

0xca841faa…486a

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x35c51188…1600

0x34b655…2a6f

4 touches
1 conflict

0x3b5fbc7d…c8fe

0x34b655…2a6f

4 touches
1 conflict

0x3fff7ccd…5a48

0x34b655…2a6f

4 touches
1 conflict

0x58620f29…db5a

0x34b655…2a6f

4 touches
1 conflict

0x5e0b8bbe…377b

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 0xca841faae5…71486a

← previous block·next block →recent activity