← previous blocknext block →recent activity

Analyzing

Block #98,839,443

18 transactions · 18 stateful · 2026-08-24 19:18:53 UTC

Parallelism

72/100

Blocked

33%

Avg conflicts / tx

0.72

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #98,839,443  ·  18 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

0x41335ddf…94b9

0x34b655…2a6f

6 touches
3 conflicts

0x7de57974…f5ba

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

4 touches
1 conflict

0xe5bb3628…e5f1

0x34b655…2a6f

4 touches
1 conflict

0x00000000…004c

0x80c745…7210

4 touches
1 conflict

0x6e3e9f18…f684

0x34b655…2a6f

4 touches
1 conflict

0x86d026f3…4cf3

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 0x41335ddf94…5594b9

← previous block·next block →recent activity