← previous blocknext block →recent activity

Analyzing

Block #98,836,681

22 transactions · 19 stateful · 2026-08-24 19:04:59 UTC

Parallelism

91/100

Blocked

26%

Avg conflicts / tx

0.23

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #98,836,681  ·  22 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

0x6ca15e14…7be8

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad04

0x34b655…2a6f

4 touches
1 conflict

0x09106a95…1467

0x33176b…e078

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x00000000…0002

0xbb3f3c…e046

4 touches
1 conflict

0xbb97db90…4c93

0xc8689a…ee79

4 touches
1 conflict

0x158f53c0…6445

0x34b655…2a6f

2 touches
0 conflicts

0x2cc1dbc9…bdd2

0x34b655…2a6f

2 touches
0 conflicts

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 0x6ca15e14f4…917be8

← previous block·next block →recent activity