← previous blocknext block →recent activity

Analyzing

Block #98,428,191

25 transactions · 21 stateful · 2026-08-23 08:13:16 UTC

Parallelism

80/100

Blocked

38%

Avg conflicts / tx

0.44

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #98,428,191  ·  25 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

0x11258774…9892

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0002

0xbb3f3c…e046

6 touches
3 conflicts

0xd0dae0c0…fcf2

0x065c9d…c394

5 touches
3 conflicts

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0xf3d7a307…4d63

0x065c9d…c394

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x00000000…003d

0xa6afd3…d132

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: Kuru Exchange: MarginAccount

3 conflicts on slot 0x1125877469…519892

← previous block·next block →recent activity