← previous blocknext block →recent activity

Analyzing

Block #85,674,916

20 transactions · 16 stateful · 2026-07-05 02:57:04 UTC

Parallelism

70/100

Blocked

44%

Avg conflicts / tx

0.75

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #85,674,916  ·  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

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

6 touches
3 conflicts

0xc5982a5c…012a

0x065c9d…c394

6 touches
3 conflicts

0x9ff176a9…152e

0x065c9d…c394

4 touches
1 conflict

0x3a7091da…f2eb

0x34b655…2a6f

4 touches
1 conflict

0x46c64ae6…6a06

0x34b655…2a6f

4 touches
1 conflict

0x49d02518…ca01

0x34b655…2a6f

4 touches
1 conflict

0x510c8ab3…95d5

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: Market-MON/USDC

10 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity