← previous blocknext block →recent activity

Analyzing

Block #98,382,142

19 transactions · 17 stateful · 2026-08-23 04:21:35 UTC

Parallelism

89/100

Blocked

18%

Avg conflicts / tx

0.16

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #98,382,142  ·  19 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x9a3068dd…18f0

0x34b655…2a6f

4 touches
1 conflict

0x9a3068dd…18f1

0x34b655…2a6f

4 touches
1 conflict

0x722cbd42…8e33

0x34b655…2a6f

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x468ea409…4294

0x34b655…2a6f

4 touches
1 conflict

0xe8f5e33f…719c

0x34b655…2a6f

4 touches
1 conflict

0xf6884b1c…8b7f

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

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

1 conflict on slot 0x9a3068dd84…9918f0

← previous block·next block →recent activity