← previous blocknext block →recent activity

Analyzing

Block #98,648,961

18 transactions · 18 stateful · 2026-08-24 03:11:28 UTC

Parallelism

61/100

Blocked

56%

Avg conflicts / tx

1.39

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #98,648,961  ·  18 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x2a9e9bd1…5368

0x2a68ba…90c5

12 touches
15 conflicts

0x11b69a7e…334e

0xee8c0e…1242

10 touches
10 conflicts

0xa1087a5c…66c4

0x754704…b603

10 touches
10 conflicts

0x8db9352d…a913

0xa6afd3…d132

9 touches
10 conflicts

0xaf30c163…0fb6

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x71717491…10cf

0xa6afd3…d132

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

15 conflicts on slot 0x2a9e9bd1e2…355368

← previous block·next block →recent activity