← previous blocknext block →recent activity

Analyzing

Block #94,978,848

17 transactions · 17 stateful · 2026-08-11 05:32:35 UTC

Parallelism

71/100

Blocked

41%

Avg conflicts / tx

0.59

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #94,978,848  ·  17 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

8 touches
6 conflicts

0xb204a485…adfb

0x065c9d…c394

7 touches
6 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x3d9eb674…b3fb

0x754704…b603

6 touches
3 conflicts

0xb0e2447c…17dc

0x754704…b603

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x260e8874…75d3

0x34b655…2a6f

4 touches
1 conflict

0x3439dfbc…0d03

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

6 conflicts on slot 0x1125877469…519892

← previous block·next block →recent activity