← previous blocknext block →recent activity

Analyzing

Block #98,926,607

20 transactions · 19 stateful · 2026-08-25 02:37:22 UTC

Parallelism

70/100

Blocked

42%

Avg conflicts / tx

0.6

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #98,926,607  ·  20 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

0x889d5e90…929a

0x2a68ba…90c5

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xbb97db90…4c93

0xc8689a…ee79

4 touches
1 conflict

0x41469894…598f

0x34b655…2a6f

4 touches
1 conflict

0x41469894…5990

0x34b655…2a6f

4 touches
1 conflict

0x3439deb5…2fa4

0x40c49f…2af0

4 touches
1 conflict

0x00000000…003d

0x40c49f…2af0

4 touches
1 conflict

0x09106a95…1467

0x33176b…e078

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

6 conflicts on slot 0x889d5e90c7…59929a

← previous block·next block →recent activity