← previous blocknext block →recent activity

Analyzing

Block #98,836,711

29 transactions · 26 stateful · 2026-08-24 19:05:08 UTC

Parallelism

79/100

Blocked

27%

Avg conflicts / tx

0.31

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #98,836,711  ·  29 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

6 touches
3 conflicts

0xca5b9231…3bd1

0x34b655…2a6f

6 touches
3 conflicts

0x33000c0a…82c3

0x34b655…2a6f

4 touches
1 conflict

0x552a92f9…bb1c

0x34b655…2a6f

4 touches
1 conflict

0x5eb187dd…b1d6

0x34b655…2a6f

4 touches
1 conflict

0x7de57974…f5ba

0x34b655…2a6f

4 touches
1 conflict

0x7ec9cda3…6ddb

0x34b655…2a6f

4 touches
1 conflict

0x84d74093…7808

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

← previous block·next block →recent activity