← previous blocknext block →recent activity

Analyzing

Block #98,083,792

19 transactions · 16 stateful · 2026-08-22 03:19:50 UTC

Parallelism

74/100

Blocked

50%

Avg conflicts / tx

0.68

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #98,083,792  ·  19 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

0x3ee8b564…4c49

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xbde524f4…43bf

0x34b655…2a6f

6 touches
3 conflicts

0xe5bb3628…e5f1

0x34b655…2a6f

4 touches
1 conflict

0x1d1ca8c8…b803

0x34b655…2a6f

4 touches
1 conflict

0x21e8ab54…3b4b

0x34b655…2a6f

4 touches
1 conflict

0x7aad02c6…b979

0x34b655…2a6f

4 touches
1 conflict

0x9482a067…eba9

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 0x3ee8b5644d…f04c49

← previous block·next block →recent activity