← previous blocknext block →recent activity

Analyzing

Block #73,653,055

22 transactions · 21 stateful · 2026-05-10 10:11:42 UTC

Parallelism

68/100

Blocked

38%

Avg conflicts / tx

1.18

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,653,055  ·  22 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

0xf2f76ab3…623e

0x2a68ba…90c5

10 touches
10 conflicts

0x046a928e…0012

0x2a68ba…90c5

10 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0x0ac31945…2c72

0x065c9d…c394

6 touches
3 conflicts

0x529acb6a…fcc6

0x065c9d…c394

4 touches
1 conflict

0xd1728230…ff9b

0x065c9d…c394

4 touches
1 conflict

0x5062a21d…c68b

0x065c9d…c394

3 touches
1 conflict

0xe7e21179…57a8

0x3c2269…cf62

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

10 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity