← previous blocknext block →recent activity

Analyzing

Block #74,977,699

8 transactions · 7 stateful · 2026-05-16 13:39:17 UTC

Parallelism

75/100

Blocked

29%

Avg conflicts / tx

0.25

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,977,699  ·  8 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

4 touches
1 conflict

0x9ad0591c…4efe

0x065c9d…c394

3 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x99f666e3…b2a2

0x3bd359…433a

2 touches
0 conflicts

0x4e368b2b…09ac

0x754704…b603

2 touches
0 conflicts

0x9194f4a3…10b8

0x754704…b603

2 touches
0 conflicts

0xa1087a5c…66c4

0x754704…b603

2 touches
0 conflicts

0xffe004da…e2f4

0x754704…b603

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

1 conflict on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity